just to let you know beta 3 iOS 12 is out I'm installing it now
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
Does anyone know if there's a way to update after installing? I updated my MacBook (7,1) on a separate partition, but that was using a Developer Beta 1 install. I went to update but it says there are none. I have installed the public beta access utility, but it still can't find any. Does anyone know? Thanks.
Cool.
[doublepost=1531934751][/doublepost]
You need to apply the software update patch from the post install tool.
Is there a way for the AMD 7xxx kext to load on a Mac Pro 2008 the Stock GPU is only getting kexts to load. I have a R9 270X also is there a Patch for SSE 4,1 Xeon on Mojave to load my Metal GPU with Lilu and whatevergreen kexts to Fix the GPU Name.
No, as the Mac Pro 3,1 doesn't support SSE4.2. Unless an SSE4.2 emulator is developed, this will never be possible. Lastly, you do not need to ask questions like this in the thread. Any info regarding hardware support will be added to the OP.
I also encountered this issue on my MacBook Pro 4,1. However, if you use dosdude1’s APFS ROM Patcher before installing Mojave it will allow native booting from an APFS partition. I just swapped out to a High Sierra drive ran the patcher and switched back to my Mojave one.
Yes, I’m aware of that patch. It’s not in the post install tools so most users won’t know about though.
Yea I agree, if I wouldn’t have looked it up I wouldn’t have known that it was even possible. I wonder if it is something that could even be incorporated into the patcher?
It could be. I’m not dosdude1 so I can’t implement but I know for a fact that it can be implemented.
Hey dosdude1, 1st, thanks for all the hard work with a patch allowing unsupported Mac to run Mojave.
Note: Some Mac's may require HFS on Startup Volume, if you can run HS, APFS should work.
Step 1> Download Patch from OP
Step 2> Format USB to HFS (Journaled). The USB drive needs to be named to OS X Base System
Step 3> Install Patch to USB
Step 4> Restart in T/M to USB>In tools menu of the patch>download the current version of Mojave.
Step 5> Do not install over an existing OS>Format drive>APFS/GUID Partition Map>from USB>run Mojave install>restart in T/M again & run> Post Install to whatever your Machine ID is>force cache rebuild>restart
EDIT:
Make sure SIP is disabled before starting.
to check in Terminal type;
csrutil status
if enabled, reboot into Recovery Mode
From Recovery Mode launch Terminal and type the following;
csrutil disable
reboot
Last edited:
It's on your macOS Mojave patcher under post install and if you click on your launchpad select other you should see patch updater close to disk utility
I'm not sure if that's something I want to implement into the patcher, as it has the potential to brick a machine if something goes wrong. I'd prefer a user to understand this risk before applying the APFS ROM patch, even though the chance of it happening is very small (only one person that I know of had something go wrong and brick their machine). With that said, if you want to enable native APFS booting on your machine, the patch can be downloaded here. Any machine that didn't natively support High Sierra will need this to boot an APFS volume.
I linked this guide on the wiki post.
[doublepost=1531944046][/doublepost]Question for Everyone:
Is anyone actually trying to find a fix for the transparency glitches in light mode or has it been classified as an unfixable issue and is being ignored?
Does APFS ROM Patcher work with MacbookAir2,1 mid 2009?
If so, would be better to patch firmware from El Capitan, Snow Leopard or indifferent?
It should work for that model and I would recommend patching from El Capitan.
I said should because I didn’t create this patch and as such I am unsure if it will work or not. I assume it will work but I am not responsible for any damage done to your machine because of you following this advice.
Yes, it'll work on the MBA2,1. Doesn't matter which OS you run it from, it should work under OS X 10.7 Lion and later.
I ran this, but it just stays on "Rebuilding caches..." forever until I press restart, and then upon restart, nothing has noticeably changed. I tried rebuilding them myself using terminal, but still nothing. It won't find any updates. Help?
Just my two cents as an early adopter of APFS booting on an unsupported machine back in the HS days. The early implementations (last year) performed some EFI wizardry (the critical hidden partition on your hard disk) that slowed down the boot process some and presented some different visuals before the familiar logo. I think dosdude1's patch follows the same general approach. In my case, the performance improvements were minimal (at best) and I'm running an old 8GB 250GB SSD on an mbp 5,3. Yes, moving files around was a little zippier and the overall technology is sound, but I feel it is more suited to the modern line of devices. Plus it complicates things when retro-fitting new OSes on our old hardware.
In the end, I opted out, reformatted the partitions to plain old HFS+, removed the EFI support files (important) and haven't regretted it since. Just my observations - your mileage may vary.
No, no, this patch is completely different. It adds native APFS support to the machine's firmware, allowing it to boot like a normal APFS-supported Mac would, with no slow-down. Observe here.
I stand corrected then: yours is obviously is a better implementation. congrats.
Still I don't see the cost benefit of APFS on my lowly 5,3 - doing just fine with HFS+ (as you mentioned a while ago)
I was also an 'early adopter' using dosdude1's APFS ROM Patch on a MB 5.2 and although it works well after the OS is running - the boot is slow. (with a long 'beep' 2 seconds long - not the start up chime - and a black screen for say 20 seconds before the normal boot process starts)
I have tried to remove it and go back to the original ROM (which the APFS ROM patcher saves for you during installation). I have been unable to get this to work. When I try I just get a message from the ROMtool.app used for this that it doesn't recognize the installed 'EPROM'. I have been unable to re-flash the ROM back to it's original state.
If anyone has any suggestions for removal of the APFS ROM Patch I'd be grateful to hear about it.
Last edited:
since you are on macOS Mojave DB 1 I would user the macOS Mojave patcher utility under tools download the macOS DB 4 then create your usb with the macOS patcher beta 12 boot into it the use disk utility format your macOS DB1 partition then install DB 4 it could be possible DB1 can not link to the DB 4 catalog
I´m one of the lucky guys who bricked an Air 2,1 with the ROM patcher. Have been in contact with another one who had this outcome. So it´s at least three.
But I have to say it worked as a charm on a bunch of other of my machines (home & office!). So I´m not sure it was just bad luck with the MBA 2,1 or it is system specific failure of the ROM patcher?
Trying APFS patcher from El Capitan (SIP disabled), it took about 5 minutes in dumping ROM/writing Patched ROM.
At the end of patching it has created in user main folder two backups:
MacbookAir2,1_APFS.bin 4,2 MB
MacbookAir2,1_backup.bin 4,2 MB
Unluckily after power off, powering on the white led stays 3 seconds with no chime sound, then turns off, after automatically turns on again and stay white solid with black screen.
Tried SMC, PRAM reset, but same result.
I think it's bricked, but it doesn't matter, I had not used it for years.
An experiment gone wrong, it can happen.