Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
MacBook Pro 5,2 - 17 inch, C2D - hybrid Segate Momentus HDD, formated in APFS. Running 10.14, original release.

Attempted to update 10.14 with each Mojave beta release, but to no avail. I did apply dosdude1's patches.

Betas 1 - 3 updates resulted in boot-loop; no discernible fix worked, other than reinstalling the system.
Betas 4 - 5 updates, would proceed to "full" progress bar, but would stall at that point.

I managed to boot into the Single User Mode, after an attempt at beta 5 install, and took a photo of the screen when progress in beta 5 installation stalled. See attached file. Examining the trace reveals, that "initial boot" completes, but progress stalls at APFS handling routines (?)
 

Attachments

  • Beta 5 trace in single user mode.jpg
    Beta 5 trace in single user mode.jpg
    3.1 MB · Views: 376
Last edited:
  • Like
Reactions: TimothyR734
MacBook Pro 5,2 - 17 inch, C2D - hybrid Segate Momentus HDD, formated in APFS. Running 10.14, original release.

Attempted to update 10.14 with each Mojave beta release, but to no avail.

Betas 1 - 3 updates resulted in boot-loop; no discernible fix worked, other than reinstalling the system.
Betas 4 - 5 updates, would proceed to "full" progress bar, but would stall at that point.

I managed to boot into the Single User Mode, after an attempt at beta 5 install, and took a photo of the screen when progress in beta 5 installation stalled. See attached file. Examining the trace reveals, that "initial boot" completes, but progress stalls at APFS handling routines (?)
Looks like something got corrupted (checksum error), maybe try:

- Recovery mode, Disk Utility, First Aid
or
- Single user mode, fsck -fy
 
All - Mojave Hybrid Mode v1.0 is released (for Mojave GM)

The screenshots should be self explanatory, but this is a "fix" for our broken Mojave Light Mode. Search back for my original posts on this. You will find it here with notes and instructions. Read them carefully.

Lots of good people collaborated on this. So a special shout out to these collaborators :
@testheit @arqueox @TimothyR734 @ASentientBot @0403979 @webg3 and others...


View attachment 797799 View attachment 797800

Many more screenshots and details are available in the repo.

This is still an active project, so updates and support for upcoming Mojave updates will be coming soon. Open an Issue if you have a problem.

More documentation and a cleaner "scripted" installation will be available when time permits. Other ways of distributing are being explored.

NOTE: For the moment it is assumed that you know what you're doing and are fairly comfortable with the Terminal command line. If you are not, proceed with caution and ask for help: there are plenty of us who tested this to help.

Nothing here will brick your machine if you follow guidelines and make some quick backups (again - read instructions carefully) Ultimately, it always pays to know how to do things manually...

Do not use if you have upgraded to a beta - while it may be compatible it is highly unrecommended as each beta needs to be analyzed, patched and released. Going forward I plan on only supporting official Mojave updates, the in-between betas are too hard to track...


Enjoy (from the team)

I certainly would like to try this hybrid mode. But the only device I have that is in the "compatibility" list is my MacBookPro5,3, which is on 10.14.1 beta 4 right now. I know that in your note that betas are not yet recommended to use or test this. What happens if I do? Also, if it's not in the compatibility list (such as MBAir4,2) can I try with any adverse affects?

Thanks @pkouame for this.
 
  • Like
Reactions: TimothyR734
I certainly would like to try this hybrid mode. But the only device I have that is in the "compatibility" list is my MacBookPro5,3, which is on 10.14.1 beta 4 right now. I know that in your note that betas are not yet recommended to use or test this. What happens if I do? Also, if it's not in the compatibility list (such as MBAir4,2) can I try with any adverse affects?

Thanks @pkouame for this.
Good questions.

  • So far these binaries have been tested on various pros, books, bookpros and imacs. Both NVidia and Intel based GPUs. It would definitely help if you gave it shot on an air 4,2. Compiling a list of tested models will eventually prove valuable. I would say that the most critical requirement before trying these is a working Mojave GM system.
  • The "hardware compatibility list" you are referring to hasn't been updated. I will do so soon (and switch its status to work in progress) Sorry for the confusion.
  • The only list officially referenced is the compatibility list, which is more of a software compatibility list tracking various checksums. These signatures are mainly used internally for my scripts that patch in-place. It can be useful to others to verify that their stock system binaries are "compatible" with the patched ones released (as you can imagine, swapping these binaries around for testing can become fairly confusing)
  • The "files" section contains original versions of the frameworks being patched. A good source if you have lost your backup and need to restore a broken system.
  • I have unofficially tried some of these on a 10.4.1beta1 and beta2 systems with no immediate adverse effect. But these were far from being exhaustive tests, so highly unrecommended. New updates will introduce new features that may or may not affect the subsystem being patched. Also, these are core frameworks accessed by other frameworks and apps, it's all highly inter-dependent. You may luck out for a short while, but it will eventually bite you. I would wait for a release that supports your point update.
Hope this helps. Refinements such as enhanced docs and scripted installs are coming soon. Stay tuned.
[doublepost=1540360491][/doublepost]
MacBook Pro 5,2 - 17 inch, C2D - hybrid Segate Momentus HDD, formated in APFS. Running 10.14, original release.

Attempted to update 10.14 with each Mojave beta release, but to no avail. I did apply dosdude1's patches.

Betas 1 - 3 updates resulted in boot-loop; no discernible fix worked, other than reinstalling the system.
Betas 4 - 5 updates, would proceed to "full" progress bar, but would stall at that point.

I managed to boot into the Single User Mode, after an attempt at beta 5 install, and took a photo of the screen when progress in beta 5 installation stalled. See attached file. Examining the trace reveals, that "initial boot" completes, but progress stalls at APFS handling routines (?)
I went through the same thing once, suspecting it had something to do with overlaying beta on top of beta over the past few months, I re-imaged all my old macs to stock Mojave GM (full install). The beta updates auto-magically became smoother. Still not sure what the issue was...both my pro 3,1 and bookpro 5,3 survived the rom updates (I guess...)
 
Good questions.

  • So far these binaries have been tested on various pros, books, bookpros and imacs. Both NVidia and Intel based GPUs. It would definitely help if you gave it shot on an air 4,2. Compiling a list of tested models will eventually prove valuable. I would say that the most critical requirement before trying these is a working Mojave GM system.
  • The "hardware compatibility list" you are referring to hasn't been updated. I will do so soon (and switch its status to work in progress) Sorry for the confusion.
  • The only list officially referenced is the compatibility list, which is more of a software compatibility list tracking various checksums. These signatures are mainly used internally for my scripts that patch in-place. It can be useful to others to verify that their stock system binaries are "compatible" with the patched ones released (as you can imagine, swapping these binaries around for testing can become fairly confusing)
  • The "files" section contains original versions of the frameworks being patched. A good source if you have lost your backup and need to restore a broken system.
  • I have unofficially tried some of these on a 10.4.1beta1 and beta2 systems with no immediate adverse effect. But these were far from being exhaustive tests, so highly unrecommended. New updates will introduce new features that may or may not affect the subsystem being patched. Also, these are core frameworks accessed by other frameworks and apps, it's all highly inter-dependent. You may luck out for a short while, but it will eventually bite you. I would wait for a release that supports your point update.
Hope this helps. Refinements such as enhanced docs and scripted installs are coming soon. Stay tuned.

Thank you for prompt response. My MBAir4,2 is on 10.14 (18A391) so I will apply it and will let you know how it goes. I'm sure it will go great. Thanks again for your work and efforts.
 
  • Like
Reactions: TimothyR734
Thank you for prompt response. My MBAir4,2 is on 10.14 (18A391) so I will apply it and will let you know how it goes. I'm sure it will go great. Thanks again for your work and efforts.
I just updated the hardware list and some notes. I will setup the wiki next week and start an FAQ.

Thanks for testing on Air - PM me, if you would like to join the team to watch the sausage being made in the private repo...Or simply post Issues with your results in the public one - it helps. Thanks again.
 
@pkouame how large is the download please? I got to over 500mb and cancelled because it seems a large .zip for such a small set of scripts :eek:

Cheers :)

Hugh

Confirmed, got ∞ downloading size on "HybridMode-Public-1.0.zip" from "release" tab too.

edit:
After a couple of re-attempts normal downloading size, mysteries of github.
My mistake, that was the source-code size, however what's inside ?
 
Last edited:
Confirmed, got ∞ downloading size on "HybridMode-Public-1.0.zip" from "release" tab too.

edit:
After a couple of re-attempts normal downloading size, mysteries of github.
My mistake, that was the source-code size, however what's inside ?
All of it downloaded for me.
 
  • Like
Reactions: TimothyR734
All - Mojave Hybrid Mode v1.0 is released (for Mojave GM)

The screenshots should be self explanatory, but this is a "fix" for our broken Mojave Light Mode. Search back for my original posts on this. You will find it here with notes and instructions. Read them carefully.

Lots of good people collaborated on this. So a special shout out to these collaborators :
@testheit @arqueox @TimothyR734 @ASentientBot @0403979 @webg3 and others...


View attachment 797799 View attachment 797800

Many more screenshots and details are available in the repo.

This is still an active project, so updates and support for upcoming Mojave updates will be coming soon. Open an Issue if you have a problem.

More documentation and a cleaner "scripted" installation will be available when time permits. Other ways of distributing are being explored.

NOTE: For the moment it is assumed that you know what you're doing and are fairly comfortable with the Terminal command line. If you are not, proceed with caution and ask for help: there are plenty of us who tested this to help.

Nothing here will brick your machine if you follow guidelines and make some quick backups (again - read instructions carefully) Ultimately, it always pays to know how to do things manually...

Do not use if you have upgraded to a beta - while it may be compatible it is highly unrecommended as each beta needs to be analyzed, patched and released. Going forward I plan on only supporting official Mojave updates, the in-between betas are too hard to track...


Enjoy (from the team)

First of all I want to express my personal thanks for your effort in this and public hybrid patch release, then I've not yet tried, but at first glance I noticed that your patched Appkit, CoreUI and HIToolBox "unix exec" are smaller in size than stock Mojave ones, instead they seems to match exactly those can find in any Mojave's BaseSystem.dmg , I term them the fork'ed version of the full frameworks.

I think you have patched from there, but why don't you have used the full frameworks ? If may I ask.
 
Last edited:
Confirmed, got ∞ downloading size on "HybridMode-Public-1.0.zip" from "release" tab too.

edit:
After a couple of re-attempts normal downloading size, mysteries of github.
My mistake, that was the source-code size, however what's inside ?
On github releases, the source archives the entire repo! Do not download those.

The zips (aptly named Flat, Hybrid and JustMenuBar) are simply zipped up combos of the appropriate binaries for each "Mode". Just unzip and you'll see. I packaged them this way just for convenience, the Files folder is organized appropriately per Mojave Release, the folder names should be intuitive.

Flat.zip =HIToolbox+AppKit = menubar fix + flat appearance
Hybrid.zip = HIToolBox+CoreUI = menubar fix + light mode vibrancy

NOTE: github suffered a major outage this weekend (reconstruction has been under way for a few days - so some things may be a little flaky) Check the github status page.

I just updated the repo Release notes accordingly.
[doublepost=1540387412][/doublepost]
First of all I want to express my personal thanks for your effort in this and public hybrid patch release, then I've not yet tried, but at first glance I noticed that your patched Appkit, CoreUI and HIToolBox "unix exec" are smaller in size than stock Mojave ones, instead they seems to match exactly those can find in any Mojave's BaseSystem.dmg , I term them the fork'ed version of the full frameworks.

I think you have patched from there, but why don't you have used the full frameworks ? If may I ask.
By choice, since only the framework binaries were touched and re-signed. No need to publish and distribute the entire framework.
They are stripped of their 32 bit images. Only the 64 bit images were patched. That accounts for the smaller size. The 32 bit images are useless in my opinion. Do you see any need to patch both?
 
I know now that Macbook Pro Mid 2010 7,1 will not update using the update tool. Everything went fine until final boot to OS and the Apple Logo and status bar appeared. Then the status bar populated to the end and just sat for hours. Reinstalled the release version.
 
  • Like
Reactions: TimothyR734
On github releases, the source archives the entire repo! Do not download those.

The zips (aptly named Flat, Hybrid and JustMenuBar) are simply zipped up combos of the appropriate binaries for each "Mode". Just unzip and you'll see. I packaged them this way just for convenience, the Files folder is organized appropriately per Mojave Release, the folder names should be intuitive.

Flat.zip =HIToolbox+AppKit = menubar fix + flat appearance
Hybrid.zip = HIToolBox+CoreUI = menubar fix + light mode vibrancy

NOTE: github suffered a major outage this weekend (reconstruction has been under way for a few days - so some things may be a little flaky) Check the github status page.

I just updated the repo Release notes accordingly.
[doublepost=1540387412][/doublepost]
By choice, since only the framework binaries were touched and re-signed. No need to publish and distribute the entire framework.
They are stripped of their 32 bit images. Only the 64 bit images were patched. That accounts for the smaller size. The 32 bit images are useless in my opinion. Do you see any need to patch both?

No, exhaustive.

edit:
Nay, for those who use old 32bit apps ?
 
Last edited:
  • Like
Reactions: TimothyR734
On github releases, the source archives the entire repo! Do not download those.

The zips (aptly named Flat, Hybrid and JustMenuBar) are simply zipped up combos of the appropriate binaries for each "Mode". Just unzip and you'll see. I packaged them this way just for convenience, the Files folder is organized appropriately per Mojave Release, the folder names should be intuitive.

Flat.zip =HIToolbox+AppKit = menubar fix + flat appearance
Hybrid.zip = HIToolBox+CoreUI = menubar fix + light mode vibrancy

NOTE: github suffered a major outage this weekend (reconstruction has been under way for a few days - so some things may be a little flaky) Check the github status page.

I just updated the repo Release notes accordingly.
[doublepost=1540387412][/doublepost]
By choice, since only the framework binaries were touched and re-signed. No need to publish and distribute the entire framework.
They are stripped of their 32 bit images. Only the 64 bit images were patched. That accounts for the smaller size. The 32 bit images are useless in my opinion. Do you see any need to patch both?

I just re-read my manual instructions and notes and I think they are pretty clear. Just in case:

To get Hybrid mode appearance in the screenshots:
  • patch HIToolbox in /S*/L*/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Versions/Current
  • patch CoreUI in /S*/L*/PrivateFrameworks/CoreUI.framework/Versions/Current
  • Use the GM 18A391 releases for both (the only ones supported even though I have a beta in the repo)

To get Flat mode appearance in the screenshots:
  • patch HIToolbox in /S*/L*/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Versions/Current
  • patch AppKit in /S*/L*/Frameworks/AppKit.framework/Versions/Current
  • Use the GM 18A391 releases for both (the only ones supported even though I have a beta in the repo)
Simple, I just re-tested the same procedure on my test box and It's all good. If you have issues, post a problem in the repo. Again, don't download the source archives! No need to, it's just github's way of packaging releases.
[doublepost=1540388901][/doublepost]
No, exhaustive.

edit:
Nay, for those who use old 32bit apps ?
I'm not supporting 32 bit apps (for the moment) Apple is deprecating heavily. I may reconsider that if we have an overwhelming need to.
 
Mojave 10.14.1 beta 5 on my unsupported MacBookPro,5,3.

Successfully updated (OTA) and patched using @dosdude1's mojave patcher app.
View attachment 797795
Thanks to all who contributed on this thread.
Hi DaniloGeekDude,

You installed the Mojave 10.14.1 beta 5 on your MacBookPro,5,3 without a problem.

MY MACBOOK PROFILE:
macOS Mojave
Version 10.14 (18A391)
MacBook Pro (15-inch, Early 2011)
Processor 2.2 GHz Intel Core i7
Memory 16 GB 1333 MHz DDR3
Graphics Intel HD Graphics 3000 512 MB


I'm having trouble installing any of the beta's on top of 10.14 (18A391) it does not finish the install.
The progress bar only shows only half way, and never moves after that. I only have the Public beta to install.

Do you have a procedure or steps I can follow for my situation with a Pubic beta install?

Thanks...
 
  • Like
Reactions: TimothyR734
Go to this site, search for 10.14.1, go the package file, go the part url, copy it, paste it, download it.
https://swscan.apple.com/content/ca...ion-snowleopard-leopard.merged-1.sucatalog.gz
[doublepost=1540392413][/doublepost]
My dock did not stay transparent after a reboot :(
Seems as if this simple terminal command is not sufficient and the patch by @pkouame needs to be tested by me instead ;)
Thanks btw for the transparency patch!
Yeah you have to redo it after log outs and restarts.
 
  • Like
Reactions: TimothyR734
@dosdude1

New poster, long time lurker

I was wondering when the APFS ROM Patcher would be returning. I had great success with MacBook Pro 5,1 and was hoping to use it on a recently acquired Mac Pro 3,1.

Thanks!
 
  • Like
Reactions: TimothyR734
On github releases, the source archives the entire repo! Do not download those.

The zips (aptly named Flat, Hybrid and JustMenuBar) are simply zipped up combos of the appropriate binaries for each "Mode". Just unzip and you'll see. I packaged them this way just for convenience, the Files folder is organized appropriately per Mojave Release, the folder names should be intuitive.

Flat.zip =HIToolbox+AppKit = menubar fix + flat appearance
Hybrid.zip = HIToolBox+CoreUI = menubar fix + light mode vibrancy

NOTE: github suffered a major outage this weekend (reconstruction has been under way for a few days - so some things may be a little flaky) Check the github status page.

I just updated the repo Release notes accordingly.
[doublepost=1540387412][/doublepost]
By choice, since only the framework binaries were touched and re-signed. No need to publish and distribute the entire framework.
They are stripped of their 32 bit images. Only the 64 bit images were patched. That accounts for the smaller size. The 32 bit images are useless in my opinion. Do you see any need to patch both?
What mean S* and L* in: cd /S*/L*/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Versions/Current????
 
  • Like
Reactions: TimothyR734
@pkouame
Juhu, I think you can add MacBook Pro 6,2 (15“ from 2010 with Intel and Nvidia graphics) to your compatibility list :cool:
(Tested: Hybrid (CoreUI + HIToolbox))

Great work!
 

Attachments

  • Bildschirmfoto 2018-10-24 um 17.09.16.png
    Bildschirmfoto 2018-10-24 um 17.09.16.png
    1.1 MB · Views: 260
  • Bildschirmfoto 2018-10-24 um 17.15.26.png
    Bildschirmfoto 2018-10-24 um 17.15.26.png
    1 MB · Views: 253
Last edited:
OMG!! Thanks Bro!!

With this Mod, my iMac Late 2009 become perfect right now!! :D

I was applied Hybrid with HIToolbar and CoreUI only.

Thanks a lot!!!

All - Mojave Hybrid Mode v1.0 is released (for Mojave GM)

The screenshots should be self explanatory, but this is a "fix" for our broken Mojave Light Mode. Search back for my original posts on this. You will find it here with notes and instructions. Read them carefully.

Lots of good people collaborated on this. So a special shout out to these collaborators :
@testheit @arqueox @TimothyR734 @ASentientBot @0403979 @webg3 and others...


View attachment 797799 View attachment 797800

Many more screenshots and details are available in the repo.

This is still an active project, so updates and support for upcoming Mojave updates will be coming soon. Open an Issue if you have a problem.

More documentation and a cleaner "scripted" installation will be available when time permits. Other ways of distributing are being explored.

NOTE: For the moment it is assumed that you know what you're doing and are fairly comfortable with the Terminal command line. If you are not, proceed with caution and ask for help: there are plenty of us who tested this to help.

Nothing here will brick your machine if you follow guidelines and make some quick backups (again - read instructions carefully) Ultimately, it always pays to know how to do things manually...

Do not use if you have upgraded to a beta - while it may be compatible it is highly unrecommended as each beta needs to be analyzed, patched and released. Going forward I plan on only supporting official Mojave updates, the in-between betas are too hard to track...


Enjoy (from the team)
All - Mojave Hybrid Mode v1.0 is released (for Mojave GM)

The screenshots should be self explanatory, but this is a "fix" for our broken Mojave Light Mode. Search back for my original posts on this. You will find it here with notes and instructions. Read them carefully.

Lots of good people collaborated on this. So a special shout out to these collaborators :
@testheit @arqueox @TimothyR734 @ASentientBot @0403979 @webg3 and others...


View attachment 797799 View attachment 797800

Many more screenshots and details are available in the repo.

This is still an active project, so updates and support for upcoming Mojave updates will be coming soon. Open an Issue if you have a problem.

More documentation and a cleaner "scripted" installation will be available when time permits. Other ways of distributing are being explored.

NOTE: For the moment it is assumed that you know what you're doing and are fairly comfortable with the Terminal command line. If you are not, proceed with caution and ask for help: there are plenty of us who tested this to help.

Nothing here will brick your machine if you follow guidelines and make some quick backups (again - read instructions carefully) Ultimately, it always pays to know how to do things manually...

Do not use if you have upgraded to a beta - while it may be compatible it is highly unrecommended as each beta needs to be analyzed, patched and released. Going forward I plan on only supporting official Mojave updates, the in-between betas are too hard to track...


Enjoy (from the team)
[doublepost=1540397018][/doublepost]
Yes you might try this after you unzip right click then show package contents scroll to macOS then open your terminal and drag airdrop enabler and drop in to terminal
I had used this app (iMac Late 2009), but seems can't transfer photo with iPhone (iOS 12.0.1)?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.