macOS 10.14 Mojave on Unsupported Macs Thread

[lefruitix]

So I have an update on the 5,1 I bricked flashing it .The good news is it lives !! I ordered a cheap eeprom reader and soic clip off amazon ( £17 ) but it was interesting experience. I practiced on mx
chip and detected and programmed the chip very quickly . The stt chip that’s on my board was different story . I had to tell it which chip ( I know it’s a cheap reader ) and after much messing around and things such as writing timeouts i managed to erase what was on eeprom and wrote my backup to it . Took nearly 5 hours !! But hey the machine now boots again so I am happy out .

I just thought I’d share in case anyone else is in the same boat . Thanks again all for the patience and suggestions
[doublepost=1535104636][/doublepost]
Have you tried the making the installer or a different usb . I had no problems on mine

I've installed Mojave with this flash drive before.

 

[saudor]

Another question about installing a new SSD. Is there any benefit to replace the optical drive with a second SSD? It’s around the same price to get the doubler along with the SSD, and I never considered this path. Would it be better to have both the HDD and the SSD, or just replace the HDD with the SSD sand use a USB-SATA converter?

I have both SSDs in my 2010 mbp. I used to have a HDD but it became annoying. It'd be spinning when i dont need it which means i have to be careful about moving the macbook around + using energy. I wrote an unmount script which helped but then after sleep it'd start spinning again

Granted, i could have always gotten another big SSD but since i already had a spare SSD, i just stuck it in there and installed mojave on it

 

[Macschrauber]

Of course, renaming a .kext into something else corresponds to unload the kext, involving auto-rebuilding the kextcache and prelinkedkernel at the next reboot, as known you don't have trail glitches cause you actually don't have both QE and CI acceleration but only a standard GPU kext loaded, exactly like the one used into the USB Mojave Installer or Recovery HD.

I have trail glitches with HD5xxx and HD6xxx when legacy video patch was made until I remove the x3000 kext. Or clean install the system without the legacy video patch. I understand that I don't benefit from the patch with those GPUs.

It looks like a misbehaviour, x3000 kext be loaded with HD5xxx / HD6xxx. But it is normal, El Capitan loads this kext also - so perfectly normal.

 

[jackluke]

I have trail glitches with HD5xxx and HD6xxx when legacy video patch was made until I remove the x3000 kext. Or clean install the system without the legacy video patch. I understand that I don't benefit from the patch with those GPUs.

But seems this should be a misbehaviour, x3000 kext be loaded with HD5xxx / HD6xxx.

Maybe this cause some problems to other GPU related things. Dont know yet if x3000 is loaded with other GPUs. Worth a second look...

I don't have Mac with AMD/ATI GPUs, but for ex. HD5000 if looking at the Extensions folder the main kexts needed for QE/CI should be:

AMD5000Controller.kext
AMDRadeonX5000GLDriver.bundle
AMDRadeonX5000.kext
AMDLegacySupport.kext
IOGraphicsFamily.kext
IOAccelerator2D.plugin
IOAcceleratorFamily2.kext
and few other

Probably the patched AMDRadeonX3000.kext is a bridge to bring Mojave legacy OpenGL Acceleration on HD5000/6000.
But that kext contains also the AMD Framebuffers, so for sure you are using w/o QE/CI just the standard AMD GPU kext identifying its properties in system profiler.

 

[Sam1998]

I guess that's it for Mojave I won't use any tool that can permanently disable my MacBook Pro 2011 into a piece of precious metal.

 

[0403979]

Does anyone know how to codesign a package as Apple? I'm thinking these steps can be used to patch an actual installer app but I don't know how to codesign the package.

- Convert disk image to read and write
- Expand OSInstall
- Edit Distribution
- Flatten OSInstall
- Codesign OSInstall
- Convert disk image to read only compressed

 

[thegurgz]

I have both SSDs in my 2010 mbp. I used to have a HDD but it became annoying. It'd be spinning when i dont need it which means i have to be careful about moving the macbook around + using energy. I wrote an unmount script which helped but then after sleep it'd start spinning again

Granted, i could have always gotten another big SSD but since i already had a spare SSD, i just stuck it in there and installed mojave on it

As for now I’ll just replace the HDD with the SSD in the main slot. If I need to, I’ll replace the optical drive with the HDD and use it to keep meaty files and/or time machine drive (both are SATA II connections so it doesn’t matter which is where) or just get a SATA to USB connector. Thanks for the input!

 

[Anto38x]

MacPro 2010 is officially supported with a Metal capable GPU.

I don't think so Czo, I wish it was, but I just downloaded a free app from the Apple Store called "OpenGL Extensions Viewer" and it states that my CPU is not Metal Compatible. So I'm gutted.... looks like High Sierra is my final macOS until I get my new MacPro (2019) or iMacPro upgrade Boooo Hoooooo...
[doublepost=1535122583][/doublepost]

If you update your GPU, HD5870 do not support Metal.

AMD HD7950 or Nvidia GTX680 are Metal v3 compatible and have "For Mac" officials models.

Looks like you are right... I just downloaded a free app from the Apple Store called "OpenGL Extensions Viewer" and it states that my CPU is not Metal Compatible. So I'm gutted.... looks like High Sierra is my final macOS until I get my new MacPro (2019) or iMacPro upgrade Boooo Hoooooo...

 

[vince22]

Another question about installing a new SSD. Is there any benefit to replace the optical drive with a second SSD? It’s around the same price to get the doubler along with the SSD, and I never considered this path. Would it be better to have both the HDD and the SSD, or just replace the HDD with the SSD sand use a USB-SATA converter?

i've used data doubler with 2 SSD, its pretty fast for data transfer.

 

[Pinarek]

i've used data doubler with 2 SSD, its pretty fast for data transfer.

sounds very interesting with the data doubler .. how does that work exactly and in which Mac do you use that? Bite more detailed info, thank very much.

 

[jackluke]

Does anyone know how to codesign a package as Apple? I'm thinking these steps can be used to patch an actual installer app but I don't know how to codesign the package.

- Convert disk image to read and write
- Expand OSInstall
- Edit Distribution
- Flatten OSInstall
- Codesign OSInstall
- Convert disk image to read only compressed

I think it isn't feasible, you can only codesign a package with developer ID, that's why for example even installing from USB Mojave Patcher SIP disabled is required, to allow third party developer signature patched kext or binary file.

 

[vince22]

sounds very interesting with the data doubler .. how does that work exactly and in which Mac do you use that? Bite more detailed info, thank very much.

it’s just a HDD/SSD caddy that replace your optical drive, I have 2012 MBP 13” with RAID setup.

 

[0403979]

I think it isn't feasible, you can only codesign a package with developer ID, that's why for example even installing from USB Mojave Patcher SIP disabled is required, to allow third party developer signature patched kext or binary file.

That’s disappointing. Someone did it here but idk how. They disappeared now.

 

[Balaur]

...
This is your main issue Legacy USB not detected, for sure you have an invalid prelinkedkernel file inside /Volumes/Mojave/System/Library/PrelinkedKernels/

Try to boot from Mojave USB Installer, Post Install, this time select ONLY any USB patch related, and "Force cache rebuild"

After done try to boot Mojave.
...

THANK YOU so much. This solved my problem. I am and posting from Mojave (18A371a). Ready for Monday DP 9

 

[hvds]

Alright, I've finally finished it... APFS ROM Patcher is finally done! Some precautions:

- APFS ROM Patcher is to be used AT YOUR OWN RISK! There is always the possibility that your machine could become bricked as a result.
- DO NOT apply APFS ROM Patcher if your machine already can boot from APFS volumes
- If you get the following dialog, it is HIGHLY RECOMMENDED that you open your machine, remove your logic board if necessary, and verify the exact EEPROM type your machine has. Selecting the wrong EEPROM model will MOST LIKELY result in a bricked system!

View attachment 776034

Download here. Please be sure to post results!

[doublepost=1535129691][/doublepost]Hi dosdude, I'm about to execute the APFS ROM patcher on my MacBoocPro5,2 (17inches, mid 2009). Before doing so, I'd still like to ask three questions:
- I've looked up the EEPROM, it is type MX25L3205DM2I-12G. I assume that is the expected type, is it? (The ROM patcher doesn't ask for that nor show it, but I thought I better crosscheck with you.)
- can I execute the ROM patcher under High Sierra or under Mojave - is there a preferred way.
- will the patched ROM boot HS as well as Mojave.
This is what I have on my MBP5,2: High Sierra 10.13.6 (17G65) on the internal SSD with APFS, and Mojave PB7 on an external (USB) SSD, also with APFS. Both boot fine without the ROM patch, showing the textual protocol during booting (I guess the APFS booting capability of my Mojave installation is a fortunate left-over from cloning (CCC) the internal SSD to the external and then installing Mojave over it with your patcher, then doing post-install where there is no APFS option).
The present boot ROM version is MBP52.008E.B05. The SN is W89301N58YB.
Thanks for your great help with the Sierra patcher, the HS patcher, the Mojave patcher, and the APFS ROM patcher.

 

[dosdude1]

[doublepost=1535129691][/doublepost]Hi dosdude, I'm about to execute the APFS ROM patcher on my MacBoocPro5,2 (17inches, mid 2009). Before doing so, I'd still like to ask three questions:
- I've looked up the EEPROM, it is type MX25L3205DM2I-12G. I assume that is the expected type, is it? (The ROM patcher doesn't ask for that nor show it, but I thought I better crosscheck with you.)
- can I execute the ROM patcher under High Sierra or under Mojave - is there a preferred way.
- will the patched ROM boot HS as well as Mojave.
This is what I have on my MBP5,2: High Sierra 10.13.6 (17G65) on the internal SSD with APFS, and Mojave PB7 on an external (USB) SSD, also with APFS. Both boot fine without the ROM patch, showing the textual protocol during booting (I guess the APFS booting capability of my Mojave installation is a fortunate left-over from cloning (CCC) the internal SSD to the external and then installing Mojave over it with your patcher, then doing post-install where there is no APFS option).
The present boot ROM version is MBP52.008E.B05. The SN is W89301N58YB.
Thanks for your great help with the Sierra patcher, the HS patcher, the Mojave patcher, and the APFS ROM patcher.

The patcher will attempt to automatically determine the EEPROM type. If it succeeds, it will continue on without any prompts. If not, it will ask you to select the specific EEPROM model. You should be able to run the patcher under any OS. It supports as old as OS X 10.7 Lion. Once patched, the system will work exactly as it did before. It will now just be able to boot APFS volumes as well.
[doublepost=1535130251][/doublepost]

Hello everyone, I've got a problem while installing Mojave with the latest Mojave patcher. MacOS post install tool doesn't work on my MB5,1. If I check it manually then it just crashes.

This happens when you use a USB drive that's too small. Make sure the drive/volume you're using is at least 16GB in size.

 

[jackluke]

That’s disappointing. Someone did it here but idk how. They disappeared now.

I don't know how to edit and correctly resign an InstallESD.dmg, but maybe it could work editing OSInstall.mpkg if the MacOS Installer is created in this way:

open the main DMG MacOS Installer typically located:
/Applications/Install\ macOS\ 10.14\ Beta.app/Contents/SharedSupport/InstallESD.dmg

Inside the mounted InstallESD.dmg there is the "BaseSystem.dmg", this dmg should be restored (using disk utility) into an empty 16 GB USB drive, then inside the mounted InstallESD.dmg there should be a /Packages folder that need to be copied/replacing manually the path:
/Volumes/YOURUSB16GBLABEL/OS\ X\ Base\ System/System/Installation

in this way you should obtain an expanded Mojave Installer inside which you could easily edit the packages.

 

[TimothyR734]

That’s disappointing. Someone did it here but idk how. They disappeared now.

You might PK Foxlet

 

[hvds]

The patcher will attempt to automatically determine the EEPROM type. If it succeeds, it will continue on without any prompts. If not, it will ask you to select the specific EEPROM model. You should be able to run the patcher under any OS. It supports as old as OS X 10.7 Lion. Once patched, the system will work exactly as it did before. It will now just be able to boot APFS volumes as well.

 

[0403979]

I don't know how to edit and correctly resign an InstallESD.dmg, but maybe it could work editing OSInstall.mpkg if the MacOS Installer is created in this way:

open the main DMG MacOS Installer typically located:
/Applications/Install\ macOS\ 10.14\ Beta.app/Contents/SharedSupport/InstallESD.dmg

Inside the mounted InstallESD.dmg there is the "BaseSystem.dmg", this dmg should be restored (using disk utility) into an empty 16 GB USB drive, then inside the mounted InstallESD.dmg there should be a /Packages folder that need to be copied/replacing manually the path:
/Volumes/YOURUSB16GBLABEL/OS\ X\ Base\ System/System/Installation

in this way you should obtain an expanded Mojave Installer inside which you could easily edit the packages.

I want to edit these packages in the actual installer app so I can install it to a partition from my normal OS.

 

[OGNerd]

I guess that's it for Mojave I won't use any tool that can permanently disable my MacBook Pro 2011 into a piece of precious metal.

No ROM modifications are required for a 2011 MBP, as it natively supports APFS.

 

[TimothyR734]

That’s disappointing. Someone did it here but idk how. They disappeared now.

maybe this works

 

[hvds]

Success - ROM patcher completed successfully on MBP5,2. Booting HS 10.13.6 (internal SSD) and Mojave PB7 (USB), both APFS, works fine. Thanks!

For others with a MBP5,2: the ROM patcher offered 3 choices for the EEPROM chip type, I selected the one previously looked up on the logic board (25L3205D), which is different from the default. The 8-pin chip is easily visible when removing the aluminum bottom, see middle of the attached photo.

The ROM patcher took about 5min to dump the EEPROM and about 10min to write it back, as dosdude said. Be sure to let the process complete...

 

[jackluke]

I want to edit these packages in the actual installer app so I can install it to a partition from my normal OS.

If you intend to install in partition directly from a MacOS booted system, then as you wrote before, you'd need to convert the DMG read/write, edit the packages, resign and recreate the DMG read-only, but I guess the main issue still remains is how codesign packages embedded into the main MacOS installer DMG.

Anyway you could try to create a manual 16 GB USB Mojave Installer following my previous steps, make your patching and then launching the "Install macOS Mojave Beta.app" inside the "OS X Base System" directly from the USB drive, in this way maybe you could try an in-place Mojave installing into another disk partition.

 

[tsialex]

I don't think so Czo, I wish it was, but I just downloaded a free app from the Apple Store called "OpenGL Extensions Viewer" and it states that my CPU is not Metal Compatible. So I'm gutted.... looks like High Sierra is my final macOS until I get my new MacPro (2019) or iMacPro upgrade Boooo Hoooooo...
[doublepost=1535122583][/doublepost]
Looks like you are right... I just downloaded a free app from the Apple Store called "OpenGL Extensions Viewer" and it states that my CPU is not Metal Compatible. So I'm gutted.... looks like High Sierra is my final macOS until I get my new MacPro (2019) or iMacPro upgrade Boooo Hoooooo...

Just replace your GPU. You have lots of options…