macOS 10.14 Mojave on Unsupported Macs Thread

[skiabox]

Guys I have my first eficheck.dump file created (I believe this thing is running once a week).
Should I worry?
Thank you all!

 

[L Caputo]

I have a MacPro 3,1 here with the APFS ROM patched boot firmware and patched High Sierra on one drive formatted as jHFS and patched Mojave on another drive formatted as APFS with no booting issues other than the option boot selector showing a phantom boot efi icon for the APFS volume in addition to the normal volume icon. The Startup Disk system preference panel is unaffected by that glitch and only shows the single expected APFS volume.

Note that dosdude1 hasn't reposted the APFS ROM patcher application yet.

Thank You, glad you have no issues, I was reluctant to use the APFS ROM patcher due to the possibility of it bricking the entire machine, lets see if dosdude1 reposts and that it is less risky to use in the future.

 

[flygbuss]

How do I undo that SIP is disabled on startup? I used the same installation for the now supported system I had patched before. Re-installing the OS didn't do the trick.. Thanks!

 

[Dannyy]

I am unable to upgrade to 10.14.1. MacBook 5,2. I'm using the final build 18A391, no updates in software update, and downloading the package manually gives me the unsupported system error. I've reinstalled the patches and still no updates.

I overwrited 10.14.1 over 10.14 without formatting hard drive. I was too lazy to find another way to do it. Long way, but work's fine.

 

[jackluke]

Hi everyone,
I haven't been on this forum for a while, and am too lazy to read through the hundreds and thousands of posts.
Would anyone be able to help me with this problem?

Many thanks in advance!

Not sure but maybe your USB label could be the issue: Mojavé
Try use a label without any language accent.

 

[Yipee2016]

Can I ask you a question about your Mac Pro 3.1. As you have installed Mojave on an APFS formatted SSD do you also have any other drives on your MP that are HFS+ and can your Mac boot between the two successfully.
My MP 3.1 has an SSD with High Sierra on it and when booting will go through the APFS verbose boot but then just switch back to booting to Sierra on my HFS+ formatted disk.

I can boot on all my hard drive.

 

[DaniloGeekDude]

Hi Danilo,

I am using the same patch version 1.2.3, but cannot upgrade tp beta 10.14.2 beta 1. Kindly let me know how you were able to get this patch. My mac is also enrolled in Apple Beta Software Program. Attached is the file if this helps.

Thank you very much for your help.

Hello. Just saw this so apologies for not responding promptly.

Saw on your screen shot that your Mac (what model is it?) is on public beta. My Macs are on the developer's seed program. But your public one should work. First of all, the boot drive where your Mojave is installed should be in APFS format. If it is in HFS, it will not work. Here's the straight forward steps I did to upgrade mine.

1. Update via OTA (System Preferences | Software Update).
2. It will take a while. What I did to speed things up myself is run this in terminal (sudo softwareupdate -da). Doing so will download initially the the update packages. You'll see when it is done downloading.
3. Then go again to OTA and click Update. It should promptly tell you to restart.
4. Will show that it restarted and display message "installing updates or something similar"
5. After it is done, boot to the Mojave Patcher USB drive, and run Mac OS Post Install. Make sure to click on "force cache rebuild" prior to rebooting.

That's it. Good luck. Let us know how it goes.

 

[rgwoehr]

Now, how do I put Mohave on this fusion machine? I'm just being smart and preparing for plan b. I'll dig up the error log and post it, but I've gotta a show to do, so in a few hours. I'm downloading 10.14.18. Is that the latest final?

Your machine is supported, even with the fusion drive. I'd recommend starting a new thread to figure out why the upgrade isn't working.

The computer was probably refurbished before Mojave was released and has just been sitting on the shelf. To me it seems like a waste of time and resources for them to unpackage every machine and keep them up to date before shipping, when the majority of the time the updates install without problems.

 

[16v]

Hello. Just saw this so apologies for not responding promptly.

Saw on your screen shot that your Mac (what model is it?) is on public beta. My Macs are on the developer's seed program. But your public one should work. First of all, the boot drive where your Mojave is installed should be in APFS format. If it is in HFS, it will not work. Here's the straight forward steps I did to upgrade mine.

1. Update via OTA (System Preferences | Software Update).
2. It will take a while. What I did to speed things up myself is run this in terminal (sudo softwareupdate -da). Doing so will download initially the the update packages. You'll see when it is done downloading.
3. Then go again to OTA and click Update. It should promptly tell you to restart.
4. Will show that it restarted and display message "installing updates or something similar"
5. After it is done, boot to the Mojave Patcher USB drive, and run Mac OS Post Install. Make sure to click on "force cache rebuild" prior to rebooting.

That's it. Good luck. Let us know how it goes.

No!
Not working

 

[OGNerd]

You know, I've reason to think that a mac machine that support natively until HighSierra, was APFS ready since Sierra 10.12.6 , so if you updated at least 10.12.6 you should try without the APFS patch post-install, because APFS patch follows another route in booting the APFS Volumes pointing to another different place, that's why some quick reboot issues, you can have only a boot.efi and prelinkedkernel and the bootloader will load until 1/3 of a generic "macOS complete booting" then will crash because can't find root paths for sbin, frameworks and so on, I have explained bad but I think it's so.
And it seems that "bless" command doesn't have more effect on APFS scheme, but only effective on HFS.

I also believe that to be the case, as High Sierra is the last supported macOS variant that is natively supported by my MBP 8,2, and it's primary drive is a HFS+/NTFS formatted HDD. It natively supports APFS, as I have been able to install and boot Mojave on APFS formatted external drives without problem. The successful update to 10.14.2b1 on an external SSD via the OTA/USB-Patcher post-install route is what prompted me to try it on the 5,2.

El Capitan (10.11.6) is the last version of macOS that is supported on the MacBook 5,2, and even the post-install APFS patch cannot be installed on it via the @dosdude1's install patcher without being performed on a machine that has native support (or a modified boot ROM). The internal drive on the machine is still a HFS+ formatted SSD with El Capitan, and I've run all subsequent macOS releases from external drives, both HDDs and SSDs.

The system and install logs indicate a problem with the update installation associated with the 5,2 being an unsupported machine.

 

[tchek]

Hi,

I just upgraded a new machine in Mojave 10.14.1, an iMac 27' 10,1 with the 1.2.3 patch on the key that had been used for another iMac 21' 10,1.

This machine was in Sierra, so I first upgraded it to Hight Sierra which put the boot's SSD into APFS.
Everything went well, thanks to your advices (thanks again @dosdude1 and ©jackluke).

I also took the opportunity to make the Recovery partition operational as ©jackluke explained here.


My question now is :

Can I reactivate the SIP without problem, because it is now deactivated on both machines?

Cheers !

 

[OGNerd]

How do I undo that SIP is disabled on startup? I used the same installation for the now supported system I had patched before. Re-installing the OS didn't do the trick.. Thanks!

Boot into Recovery, in Terminal enter csrutil enable, reboot.

 

[dosdude1]

Hi,

I just upgraded a new machine in Mojave 10.14.1, an iMac 27' 10,1 with the 1.2.3 patch on the key that had been used for another iMac 21' 10,1.

This machine was in Sierra, so I first upgraded it to Hight Sierra which put the boot's SSD into APFS.
Everything went well, thanks to your advices (thanks again @dosdude1 and ©jackluke).

I also took the opportunity to make the Recovery partition operational as ©jackluke explained here.


My question now is :

Can I reactivate the SIP without problem, because it is now deactivated on both machines?

Cheers !

SIP must remain disabled, and WILL remain disabled when running Mojave with my patch, regardless of what you do. You can run csrutil enable as many times as you want, but SIP will still remain disabled.

 

[ptkovsky]

Hi guys!

Seems like there should be quite a bit of technology gurus sitting around here. And people should have at least some experience in Mac troubleshooting, installing hacked systems and a bit of bash knowledge, obviously.

So for me it all started after installing dosdude1's Mojave with all the patches. It booted up and worked fine afterwards. Didn't like the font and greyish things but whatever. Trouble started when 10.14.1 update via standard system OTA method came in and got installed like I did it lots of times before. But I forgot about patching it afterwards, so the system rebooted and never started again. And now I'm kind of stuck on the "Install macOS" screen, booted up from usb flash drive with that hacked installer sitting on it.

Now this goes very interesting form here, as it says that there is not enough disk space to install the OS when I keep deleting stuff. Really weird, actually.

So when working with Terminal,

du

wasn't working at first, so I found out that you can do

for path in echo /Volumes/Macintosh\ HD/{sbin,bin,usr/{sbin,bin}}; do PATH=$path:$PATH; done

and it went fine after this trick.

df -h

says that there is about 7.5 Gigs of free space.

But whenever I

rm -rf

something that weights a lot, or whatever else, it actually does disappear from the

ls

output, so the file or folder seems gone, but free space never recovers! Is this like a kind of garbage collection/not doing TRIM command on ssd disk issue, because of the limited recovery environment? Are there any other commands? I'm not sure... Already deleted lots of stuff, but it still sits at 7.5 GB! So how do I get some free space for the installation to continue? Yeah, some of it definitely got soaked with partial install of the system being not finished, too, and that adds some complexity.

It's ridiculous at this point. Getting kind of desperate too, because I would like to install this over my old system I had about 7 years for now, not quite ready for the clean wipe of the disk yet. Would you guys be so kind to assist me in googling or actually helping with what the heck do I do with my machine to get it back working? Will do the wipe (format partition with a clean install) if this all doesn't help, but still hoping for the better outcome. Yeah, I know I should be doing backups, but I didn't. Any ideas would help a lot actually! And thanks for reading this wall of text too.

 

[tchek]

SIP must remain disabled, and WILL remain disabled when running Mojave with my patch, regardless of what you do. You can run csrutil enable as many times as you want, but SIP will still remain disabled.

Well, thanks for the info.

 

[DaniloGeekDude]

No!
Not working

Too bad. Where did it fail? Can you be more specific?

 

[flygbuss]

Boot into Recovery, in Terminal enter csrutil enable, reboot.

SIP must remain disabled, and WILL remain disabled when running Mojave with my patch, regardless of what you do. You can run csrutil enable as many times as you want, but SIP will still remain disabled.

That's exactly my point. I tried to activate it the way you described @OGNerd but I remembered that the patch keeps it disabled.
How can I disable that? It doesn't have to stay disabled any longer since the machine does support now support mojave.

 

[16v]

Too bad. Where did it fail? Can you be more specific?

This
https://forums.macrumors.com/index.php?posts/26753974

 

[dosdude1]

That's exactly my point. I tried to activate it the way you described @OGNerd but I remembered that the patch keeps it disabled.
How can I disable that? It doesn't have to stay disabled any longer since the machine does support now support mojave.

Just remove SIPManager.kext from /Library/Extensions, and rebuild kextcache. But, it's not a huge deal to have SIP disabled, as it provides little to no security improvement over not having it on at all. Just makes installing some software more of a chore.

 

[OGNerd]

[Deleted]

 

[dosdude1]

Hi guys!

Seems like there should be quite a bit of technology gurus sitting around here. And people should have at least some experience in Mac troubleshooting, installing hacked systems and a bit of bash knowledge, obviously.

So for me it all started after installing dosdude1's Mojave with all the patches. It booted up and worked fine afterwards. Didn't like the font and greyish things but whatever. Trouble started when 10.14.1 update via standard system OTA method came in and got installed like I did it lots of times before. But I forgot about patching it afterwards, so the system rebooted and never started again. And now I'm kind of stuck on the "Install macOS" screen, booted up from usb flash drive with that hacked installer sitting on it.

Now this goes very interesting form here, as it says that there is not enough disk space to install the OS when I keep deleting stuff. Really weird, actually.

So when working with Terminal,

du

wasn't working at first, so I found out that you can do

for path in echo /Volumes/Macintosh\ HD/{sbin,bin,usr/{sbin,bin}}; do PATH=$path:$PATH; done

and it went fine after this trick.

df -h

says that there is about 7.5 Gigs of free space.

But whenever I

rm -rf

something that weights a lot, or whatever else, it actually does disappear from the

ls

output, so the file or folder seems gone, but free space never recovers! Is this like a kind of garbage collection/not doing TRIM command on ssd disk issue, because of the limited recovery environment? Are there any other commands? I'm not sure... Already deleted lots of stuff, but it still sits at 7.5 GB! So how do I get some free space for the installation to continue? Yeah, some of it definitely got soaked with partial install of the system being not finished, too, and that adds some complexity.

It's ridiculous at this point. Getting kind of desperate too, because I would like to install this over my old system I had about 7 years for now, not quite ready for the clean wipe of the disk yet. Would you guys be so kind to assist me in googling or actually helping with what the heck do I do with my machine to get it back working? Will do the wipe (format partition with a clean install) if this all doesn't help, but still hoping for the better outcome. Yeah, I know I should be doing backups, but I didn't. Any ideas would help a lot actually! And thanks for reading this wall of text too.

Is the drive encrypted? If so, you need to mount it in Disk Utility when booted off the USB installer, and then install the system.

 

[Mikki77]

10.14.1 working well here on an iMac 11,1 (27" late 2009), running now off APFS.
Night Shift (CoreBrightness) is broken though.
Any idea if this is just a minor issue that will be fixed soon through @dosdude1 patch updater tool?
Thanks for all the great work! My little financial contribution is on the way...

 

[ptkovsky]

Is the drive encrypted? If so, you need to mount it in Disk Utility when booted off the USB installer, and then install the system.

Hello! Thanks for showing interest in my issue, very much appreciated! It's definitely not encrypted, never used it for serious stuff so didn't try to. Drive looks like it's already mounted after boot from USB. You can

cd Volumes/Macintosh\ HD/

and other stuff. Starting Disk Utility shows Macintosh HD APFS Volume container on Apple SSD TS128C Media. This is MacBookAir4,2. So I can see the structure of the file system with files and folders using bash commands, as I described earlier. I just delete them and don't get the free space back. Maybe I'm missing something very obvious? Is the syntax correct? Is there any other way? Thanks for trying to help! I'm thinking about this situation for the past few days and didn't find any working solution yet...

 

[Edgecrusherr]

I keep getting an error when trying to make a 10.14.1 installer. This is on a 2018 MBP already running 10.14.1 to a USB drive that I've been using to make and replace the installer with every OS version since the first beta. I Even wiped the drive. It's a 64GB USB drive with a 26GB partition for the patch installer (the rest of the space is for software I use after installing. Error below. Any one have a clue?

Failed
Mounting failed. Please check your macOS Mojave Installer App, then run the tool again.

Verbose reports:
hdiutil: attach failed - Resource busy

 

[sagitt]

Works fine on my macmini5,1
with less trasparency all graphics bugs are gone

i've only 1 problem

i'm using 1ssd+1hdd with a fusion drive (done manually with terminal)

after the upgrade from high sierra to mojave i'm not able to enter in recovery mode (prohibition image after pressing cmd+r during boot)

there is a way to restore the recovery mode? the post-install "recovery patch" won't work, close the patching tool.

With "diskutil"command i can see recovery HD but won't works.

I already read the recovery fix but it's only for AFPS volumes, my Fusion Drive is not AFPS.