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.
USB Installer.
[doublepost=1541003358][/doublepost]

Agree, but on any APFS scheme/container is mandatory to have the APFS Recovery, it's just a plus emergency partition (CMD+R) where you can use always useful standard Utilities (DiskUtility, TimeMachine, Terminal and few other) saving a bit of USB power.

That said your USB Mojave Installer is also an ultra-improved Recovery.

You included too the "Recovery HD HFS patch".

I suspect part of dosdude1's ambivalence about the Recovery Volume is that patching it for unsupported machines will break the ability to cleanly apply Software Updates (when they occur without associated firmware patches).
 
  • Like
Reactions: TimothyR734
I suspect part of dosdude1's ambivalence about the Recovery Volume is that patching it for unsupported machines will break the ability to cleanly apply Software Updates (when they occur without associated firmware patches).

No, I think that is the opposite, if you have a whole APFS scheme/container the software updates will find less issues. Especially adjusting the APFS Recovery as I explained in the "part2" earlier.

You can't patch the APFS Recovery from the Post-Install but only the HFS Recovery and its option is greyed when you have an APFS Volume, so it can't break nothing.

Some people previously to save a few disk space have deleted the APFS Recovery content, but no one can get totally rid of it, will remain always a residual, unless destroy the APFS structure. That's why my concern to make it workable, we have it's a plus, we can use Utilities, Safari to surf the web and find some Terminal command we need, and for example disable SIP, adding nvram boot-args "-no_compat_check" from there, and many little things if we don't have the USB-drive in the pocket.
 
Last edited:
@dosdude1 Can't create patched USB with new patcher 1.2.3 coz it needs minimum 10Gb or more USB stick. BUT! I normally created patched USB stick and installed system with 1.2.2 earlier on same USB stick ( 8Gb ). Don't have 16Gb stick right now. How can I disable this new free space check in 1.2.3 Mojave Patcher? Tried to view package contents but can't find needed string in a configuration files. What can I do?
 
Last edited:
  • Like
Reactions: TimothyR734
I don't use the APFS patch (I have native APFS) so I don't have boot.log and I don't know how it works.


Meanwhile about fixing Bluetooth devices into the APFS Recovery try this:

Boot normally Mojave then open as you already know your /Volumes/Recovery/Random-numbers-letters/

delete the immutablekernel inside

now keeping this finder window opened, plug and open the USB Mojave Patcher and navigate into the USB path /System/Library/Prelinkedkernels/

copy the prelinkedkernel from the USB Mojave Patcher into your /Volumes/Recovery/Random-numbers-letters/

while inside /Volumes/Recovery/Random-numbers-letters/ rename this fresh copied file from prelinkedkernel to immutablekernel

reboot with CMD+R now bluetooth devices on APFS Recovery should work.

Dont get it. I deleted immutablekernel

Open USB Installer
here is the inside; There is two locked files. Should I copy those two files to /Volumes/Recovery/Random-numbers-letters/ or just prelinkedkernel?

Screen Shot 2018-10-31 at 20.52.35.png
 
Hey guys. How long it takes to update from 10.14 to 10.14.1? And is it necessary if i have only visual problems on my current version, like fozzy font, blurred/cropped edges on windows, or known problems with light mode. Thanks.
 
  • Like
Reactions: cecil444
Dont get it. I deleted immutablekernel

Open USB Installer
here is the inside; There is two locked files. Should I copy those two files to /Volumes/Recovery/Random-numbers-letters/

View attachment 799954

Just highlight the locked file press CMD+i (get info) and uncheck "locked" to unlock otherwise you can't rename it after you copy.

I am not sure if dosdude1 has patched also the immutablekernel, but for safety try copy only prelinkedkernel into your /Volumes/Recovery/Random-numbers-letters/ path and rename into immutablekernel and rebooting in CMD+R check if bluetooth input devices work.
 
Hey guys. How long it takes to update from 10.14 to 10.14.1? And is it necessary if i have only visual problems on my current version, like fozzy font, blurred/cropped edges on windows, or known problems with light mode. Thanks.

I don't believe that this is doable for the time being.
You'd better try a clean installation.
 
  • Like
Reactions: TimothyR734
Just highlight the locked file press CMD+i (get info) and uncheck "locked" to unlock otherwise you can't rename it after you copy.

I am not sure if dosdude1 has patched also the immutablekernel, but for safety try copy only prelinkedkernel into your /Volumes/Recovery/Random-numbers-letters/ path and rename into immutablekernel and rebooting in CMD+R check if bluetooth input devices work.

Didnt work I lost Recovery and getting same error here;

macOS 10.14 Mojave on Unsupported Macs Thread
 
  • Like
Reactions: TimothyR734
Didnt work I lost Recovery and getting same error here;

macOS 10.14 Mojave on Unsupported Macs Thread

You haven't lost nothing, you have only missed something, please check the steps:

- take (copy) the prelinkedkernel from the /USB Installer/System/Library/Prelinkedkernels/

- copy it over here /Volumes/Recovery/Random-numbers-letters/

- Inside here /Volumes/Recovery/Random-numbers-letters/ rename the fresh copied prelinkedkernel into immutablekernel

check renaming it correctly into "immutablekernel" for ex. if you typed "imutablekernel" it won't boot of course.
 
Last edited:
No, I think that is the opposite, if you have a whole APFS scheme/container the software updates will find less issues. Especially adjusting the APFS Recovery as I explained in the "part2" earlier.

You can't patch the APFS Recovery from the Post-Install but only the HFS Recovery and its option is greyed when you have an APFS Volume, so it can't break nothing.

Some people previously to save a few disk space have deleted the APFS Recovery content, but no one can get totally rid of it, will remain always a residual, unless destroy the APFS structure. That's why my concern to make it workable, we have it's a plus, we can use Utilities, Safari to surf the web and find some Terminal command we need, and for example disable SIP, adding nvram boot-args "-no_compat_check" from there, and many little things if we don't have the USB-drive in the pocket.

My understanding was that the Software Updates to the Recovery Partition were performing checks for the integrity of the installed files and patched copies broke that process.
 
  • Like
Reactions: jackluke
My understanding was that the Software Updates to the Recovery Partition were performing checks for the integrity of the installed files and patched copies broke that process.

My mistake, I misunderstood, but in fact into my post I suggested to rename the patched files into filenamebackup, not to delete them, just in case.

So re-renaming the backups into their default names the APFS Recovery turns back in its original state. Anyway I don't think, many failed the upgrade even without never attempted my APFS Recovery fix.
 
  • Like
Reactions: TimothyR734
You haven't lost nothing, I have only missed something, please check the steps:

- take (copy) the prelinkedkernel from the /USB Installer/System/Library/Prelinkedkernels/

- copy it over here /Volumes/Recovery/Random-numbers-letters/

- Inside here /Volumes/Recovery/Random-numbers-letters/ rename the fresh copied prelinkedkernel into immutablekernel

check renaming it correctly into "immutablekernel" if you typed "imutablekernel" it won't boot of course.

Finally it came and Magic Mouse and Keyboard are working ;) Thank you @jackluke

BTW do you know how to make APFS ROM patch? or is there any guide?
 
10.14.1 installed perfectly on my 2009 5,1 Mac Pro with a GT 120 (using the new tool, downloading 10.14.1 from Apple, putting it on a USB stick, and booting from it). The graphical glitches all remain, however, and iBooks Author–the one piece of software I still need–is completely unusable.

Screen Shot 2018-10-31 at 2.33.20 PM.png

nVidia has also said that they will not be releasing a new web driver for Mojave, so I have to wipe my installation and return to High Sierra, never updating again, because my GTX 980 won’t work without a separate driver.

So thanks, nVidia, for abandoning OS X. And thanks, Apple, for abandoning your professional market. “Buy a $500 eGPU box and plug it in separately” is not an acceptable answer. “You can’t use any GPU other than what we sell” is not an acceptable answer. “You can’t ever update your computer’s hardware” is not an acceptable answer.
 
My update experience to 10.14.1:

- Early 2011 15" MacBook Pro (8,2) - In-place install over 10.14.0 APFS formatted partition of external SSD using @dosdude1's Mojave Installer v1.2.3 to download v14.1.0 of the Install macOS Mojave.app, create an installer USB stick, perform the installation, and apply the post-install patches. Went smoothly with no issues.

- Same machine, in-place install over 10.14.0 on HPFS+ formatted partition of same SSD. Went smoothly with no issues.

- Mid 2009 13" MacBook (5,2) - in-place install over 10.14.0 on HPFS+ formatted partition of USB connected HDD. Used same installer USB stick as for MBP 8,2 update, installation and post install went smoothly, but initial boot into 10.14.1 took several minutes to complete.

- Same machine, but with 10.14.0 on APFS formatted volume of externally attached SSD. Installation and post install patching appeared to complete without issue, -BUT- the machine failed to boot into 10.14.1, instead booting into EL Capitan on the internal SSD. The APFS container was corrupted, and non-repairable. Wiped drive and performed fresh install.
[doublepost=1541015487][/doublepost]
I'm running 10.14 on a Fusion Drive formatted in HFS+.

If I run the USB installer to update to 10.14.1, what are my chances of success?

I'd say very good.
 
I suggest we postpone the talk about making the useless Recovery work. At this moment it only spams the conversation here. Let us focus on successfully updating from 14.0 to 14.1. Some are still having issues and that is more important. Next we need an updated Light/Dark mode from @pkouame. And once all of this is cleared we can continue experimenting with things like proving a point by making Recovery work. There is plenty of time to waste until 14.2 (not earlier than 1-2 months from now)
 
Last edited:
I suggest we postpone the talk about making the useless Recovery work. At this moment it only spams the conversation here. Let us focus on successfully updating from 14.0 to 14.1. Some are still having issues and that is more important. Next we need an updated Light/Dark mode from @pkouame. And once all of this is cleared we can continue experimenting with things like proving a point by making Recovery work. There is plenty of time to waste until 14.2 (not earlier than 1-2 months from now)
People are just sharing their creations to solve problems they have. If that's what they want to focus on then let them do that.
 
Hi everyone
I tried to install mojave on my mac pro 3,1 with the macOS Mojave Patcher app. I did everything as I was supposed to but when I try to boot from the usb to install mojave it just stuck with the prohibitory sign.
any suggestion?
Thanks
 
  • Like
Reactions: TimothyR734
People are just sharing their creations to solve problems they have. If that's what they want to focus on then let them do that.
If a given group of people couldn't see how structure and organization would boost their success, than they would destine themselves to running and running in circles with only marginal advances.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.