If so, lucky you.
I asked if the problem was widespread, got at least a couple of affirmative feedbacks in addition to various machines of me (different platforms CPU / GPU wise).
Again, if you do not need it, fine.
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
I asked if the problem was widespread, got at least a couple of affirmative feedbacks in addition to various machines of me (different platforms CPU / GPU wise).
Again, if you do not need it, fine.
You mean later? Yes. But it’s about 1.5Gb... BTW, I downloaded 3 times the mojave dmg, just in case...
If, for example, I try to boot MBP2011 with that usb, it shows the forbidden symbol.
Last edited:
Which Mac OS X/macOS do you use to create a patched USB installer?
Do you actually named your 16Gb USB an "OS X Base System"(when you formatted it in HFS+)?
All 4 USB that you tried are different brands(it might be easier just to create a 16Gb partition on your drive)?
I have a suspicion that you might have better luck using High Sierra or earlier OS to create your patched USB.
I guess this is exactly the moment when you learn the true value of dual(or even triple) booting your system.
You might just need to find a friend or a family member with a Mac.
Obviously it is a must to have more than one Mac if you are willing to undertake any experiments with your system.
Have you tried after "disk5 eject" to wait for other 15-30 minutes letting it complete ?
Because some USB drives starting with a fast R/W ratio, but after filling their 50% of capacity, then become suddenly very slow, don't forget that Mojave OSX Installer, apart an important Core.pkg (5,3 Gb), does contain additional tens of thousands little files between frameworks, binary and so on, just to say another, even a "single kext" can contain more than one hundred (small) files, so the bytes copy process it's slower than expected.
Last edited:
You are absolutely right about the speakers. I knew that my speakers are working but did not pick up on the sound not being that good(there goes my potential sound engineer career). My right speaker was completely torn, so I fixed it with a rubber filling compound. Now I can enjoy a more pronounced and clear startup chime. While it might not be that important the absence of a startup chime was really bugging me(it is part of Mac experience after all).
This is just another example why I like this thread. Local snapshots might be an old news for everybody else but for me it is something new that I just learned.
I had addressed the matter too, a while ago apfs local snapshots
but I add an important issue (reported by others), not only the APFS local snapshots but even a TimeMachine created over an APFS Volume will work only if the machine has a native APFS BOOTROM (tipically all those produced after 2009/2010), APFS ROM-patched ones only work with HFS+ Volume.
I know TimeMachine backups are saved over HFS+ external disks, but their "Restoring" over an APFS Volume will fail if it's APFS-ROM Patched.
Nice work! It just proves how much info is already in this thread. It is simply impossible to come up with something new, all is left is just a repetition of the same old ideas.
Last edited:
The issue is divided between 50:50 USB drive & incompatibility of @dosdude1's Mojave Patcher with Mojave. I have tried at least 6 USB sticks, before I found one that worked - even connected an HDD dock. However that one USB stick only worked when using the Patcher with an older OS - in my case El Capitan.
[doublepost=1553270534][/doublepost]
Tried 2-3 times in multiple variations, same result for my MB 4,1 - or maybe it's a 5,1 even idk anymore.
Last edited:
Probably enforcing with "sudo" TM (TimeMachine) snapshots are also create-able from a machine APFS-ROM patched, but in "Restoring" from a Recovery environment they will stop, probably2 there is some kind of EFI ROM ID verification at lower level for APFS.
Instead the HFS+ Mojave installation with TimeMachine in HFS (not localsnapshots APFS exclusive feature) work fine on unsupported mac.
4,1s are currently incapable of booting to the installer on either patcher. This might change soon for mine but dosdude has already stated that he does not plan to support the 4,1 in any way.
I thought your original reply, asking for the video, well knowing it was a MB 4,1(!), intended that it should work and that there was no way it wouldn't, hence asking for a evidence video to "proof" I'm actually doing everything right.
Also the original front page post claims:
I don’t remember reading it was a 4,1. I guess I’m mistaken. I apologise. As for the wiki, it says preliminary. The specifics are not noted there. If you want to use Mojave on a 4,1 right now then install and patch from another device. Installer support should be available soon enough.
[doublepost=1553273757][/doublepost]I read your first post and you mentioned it was a 5,1 which is impossible. It’s most likely a 4,1 which explains why it doesn’t work. Btw, the 5,1 was the aluminium MacBook. I think you meant 5,2 but it’s not that one either.
Last edited:
I tried it with "sudo" to no avail. TimeMachine/Recovery environment seems to be very smart as it did not allow me to restore even Sierra on HFS+. I can restore without any issues anything from Leopard to El Capitan(officially supported systems).
I don't own that MB4,1 , but I have tested the @Larsvonhier prelinkedkernel and it works even on supported mac, so to try make bootable the Mojave OSX Installer on your MB4,1 , boot from any yours working macOS system and download this file
then copy it from Finder overwriting and replacing the one inside your USB Installer into this path: /YourUSBNAME/System/Library/Prelinkedkernels/
then reboot, if you want too see the verbose screen, after you hold alt-option, highlight with the arrows your USB Installer, then hold CMD+V, keep holding press Enter-key on the USB Installer, after release CMD+V.
Ok, so right now I can confirm problem is burning patch with mojave os. I tried flashing the high sierra version, on a mojave laptop, and still getting error, so is something with permissions.
Let’s hope @dosdude1 can solve it!
Does this guy read even further than the last post? lol
Honestly just use Julian's Patcher. Seems way quicker too.
Which btw reminds me @0403979 – I installed macOS Mojave on a HD on another Mac, patched MB 4,1 and reinserted the drive in the MB 4,1. However mouse and keyboard don't seem to work even after multiple reboots. Same's for the USB plugs. Any ideas?
Honestly just use Julian's Patcher. Seems way quicker too.
Which btw reminds me @0403979 – I installed macOS Mojave on a HD on another Mac, patched MB 4,1 and reinserted the drive in the MB 4,1. However mouse and keyboard don't seem to work even after multiple reboots. Same's for the USB plugs. Any ideas?
