macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

I’m using a 8gb usb but will try my 16gb in the morning. Btw make sure that person is a reliable source I download a developers profile on my iPhone 6 did the install and it bricked my iPhone

As far I remember 8 GB USB weren't neither suffice to create a Yosemite installer.
Never trust a developer who shares his developer profile publicly, if he does, he knows for sure why he's doing it (ex. retrieve sensitive infos about your device).

edit:
Anyway by now the Mojave/iOS12 public beta testing program is almost aligned to the DP one, so there is no need to stumble across those roads.

 

[0403979]

Make sure that person is a reliable source I download a developers profile on my iPhone 6 did the install and it bricked my iPhone

It’s not easy to modify a beta profile (AFAIK) and I have no reason to believe that this person is untrustworthy. He’s probably just some guy that downloaded the profiles and posted them.

Yes it against the forum rules someone had a link for iOS 12 developers profile it’s was quickly removed and there is a warming on the OP for this thread just be careful

I saw the warning. That warning doesn’t mean that it’s against forum rules though but I don’t want to find out the hard way if it is.

Never trust a developer who shares his developer profile publicly, if he does, he knows why he's doing.

I trust him. I hope that’s not a bad decision.

 

[tsialex]

I saw the warning. That warning doesn’t mean that it’s against forum rules though but I don’t want to find out the hard way if it is.

It's on the first post, this topic didn't even be brought up.

Moderator Note:

Please do not ask for, or provide help getting developers profile information to access unauthorised beta software on MacRumors. If you are not a developer, sign up to the Apple Beta Software Program to get the official public beta releases.

 

[0403979]

For anyone who’s interested you can find old versions of the patcher here

 

[Aletancredo]

For anyone who’s interested you can find old versions of the patcher here

Thanks, using this patch I can download the mojave beta 4 dev correct?

 

[0403979]

Thanks, using this patch I can download the mojave beta 4 dev correct?

Yes, but there is currently an issue with installing macOS. However, you can still patch your device.

 

[Aletancredo]

Yes, but there is currently an issue with installing macOS. However, you can still patch your device.

I downloaded the old versions and I will try again. I am running macos mojave but it is beta 2 dev and I would like to upgrade to the beta 4 dev. Thank you Julian

 

[0403979]

I downloaded the old versions and I will try again. I am running macos mojave but it is beta 2 dev and I would like to upgrade to the beta 4 dev. Thank you Julian

Don’t use the older versions. Download the latest one here. The public version of the developer beta 4 hasn’t been released yet. Wait a couple of days for it to be released or purchase a developer account to download the developer profile. Once you have the profile. install it on Mojave and download beta 4 from the Software Updates pane in System Preferences. After you install the update, boot to your patched usb and run the post install patches again.

 

[Larsvonhier]

Hi @dosdude1
A minor issue on MacBook Air 4,1.
I updated to 10.14 beta 4 and re-applied patches with your 01b11.
Audio does not work, despite I checked the legacy audio selector.
I then re-copied the AppleHDA.kext from 10.13.6 back to the MB Air 4,1 and audio is ok again.
I attach the working kext here, so you might include it (again?) for the MBA4,1 (11,6").

 

[AwlsomeAlex]

Hi @dosdude1
A minor issue on MacBook Air 4,1.
I updated to 10.14 beta 4 and re-applied patches with your 01b11.
Audio does not work, despite I checked the legacy audio selector.
I then re-copied the AppleHDA.kext from 10.13.6 back to the MB Air 4,1 and audio is ok again.
I attach the working kext here, so you might include it (again?) for the MBA4,1 (11,6").

Apples changing things faster than I change Operating Systems.... maybe next time a suggestion would be to wait for the Public Release as dosdude1 would have enough time to fix small bugs like this. But since you know what you’re doing go nuts.

 

[redheeler]

I'm not sure if anybody wants this information, but I might as well share it. I never use the automated macOS downloaders. Since day one I just downloaded the files from the software catalog by hand. (I just got beta 4 this way.) If anybody else wants to know how to do that...


1. Download the software catalog. This year's is https://swscan.apple.com/content/ca...n-lion-snowleopard-leopard.merged-1.sucatalog but they always follow the same pattern. Next year's will just be ...index-10.15seed-10.15-10.14... so you can do what I do and grab a copy the moment it's released to developers without waiting for somebody to upload the beta access utility.

2. Open it in a text editor.

3. Search for InstallAssistantAuto.smd and go to the last instance of that.

4. From the point you're at, find the next instance of RecoveryHDMetaDmg.pkg and download that link.

5. Do the same for InstallESDDmg.pkg and InstallAssistantAuto.pkg. They should all be close together inside a "Packages" dict.

6. Extract the contents of the packages and the payload of InstallAssistantAuto.pkg (use a pbzx parser). You should end up with the install app, InstallESD.dmg, and RecoveryHDMeta.dmg.

7. Show package contents on the app and go to Contents/SharedSupport. Copy InstallESD.dmg into here.

8. Mount RecoveryHDMeta.dmg and copy the contents of the virtual disk into SharedSupport too.


These steps, without fail since at least macOS Sierra, will produce a functioning copy of the install app without needing an Apple ID, developer ID, or supported Mac.

Since there are now automatic download scripts, there's no real reason to follow these steps. I figured I'd share them for academic purposes only, if anyone wants to make their own automated downloader or whatever.

Edit: I've never actually looked at the code for the automated downloaders. I assume that they use this same process, though.

Nice (but somewhat involved) method of producing a full installer (rather than the empty shell installer app the App Store often provides). Thanks.

I do have a somewhat related question: Is there a fix to bypass the model check which prevents the updates from appearing and installing normally through Software Update?

 

[0403979]

Is there a fix to bypass the model check which prevents the updates from appearing and installing normally through Software Update?

Why would you need that? To install Mojave you need to download the app, not install the update.

 

[L Caputo]

Mmmm tried Patcher 1b11 and Beta 4 installer on two USBs both end up with the unable to install screen, tried saving the log but cannot find it any where.
So booting up from the installer USB get light grey screen with Apple logo and progress bar, then moves to slightly darker grey screen with the Disk Utility, Terminal and Post Install Patch panel which stays for approx 3 seconds, no main installer window appears, now goes to black screen with white Apple ad progress bar, very quick and opens the log page with the message that the OS couldn't be installed.

Let us know when this is resolved.
Thanks.

 

[0403979]

Mmmm tried Patcher 1b11 and Beta 4 installer on two USBs both end up with the unable to install screen, tried saving the log but cannot find it any where.
So booting up from the installer USB get light grey screen with Apple logo and progress bar, then moves to slightly darker grey screen with the Disk Utility, Terminal and Post Install Patch panel which stays for approx 3 seconds, no main installer window appears, now goes to black screen with white Apple ad progress bar, very quick and opens the log page with the message that the OS couldn't be installed.

Let us know when this is resolved.
Thanks.

A couple other users and I have had the same problem. Dosdude1 needs to update the patcher again. Wait for him to do that and then try again.

 

[redheeler]

Why would you need that? To install Mojave you need to download the app, not install the update.

I'm running beta 3 on the 2011 MacBook Pro 8,3, would like to update to beta 4. However, due to hidden model check, Software Update doesn't display the necessary update (erroneously claims it is up-to-date).

 

[0403979]

I'm running beta 3 on the 2011 MacBook Pro 8,3, would like to update to beta 4. However, due to hidden model check, Software Update doesn't display the necessary update (erroneously claims it is up-to-date).

Do you have the developer profile installed?

 

[Starplayr]

On the Mac Pro 3,1 and have an AMD 7xxx GPU, if you run the video patches, it will boot to GUI w/o graphics acceleration. If you do not run the patches, it will boot to a white or black screen or KP. This was on beta 3. Have not tried beta 4 yet, but results should be the same.

Starting to experiment with SSE4.2 emulation and see if the 4.2 kexts' can be loaded with emulation turned on. It looks like if you globally turn on Intel SDE, you should be able to.

 

[redheeler]

Do you have the developer profile installed?

Yes. I had previously used a supported Mac to update it from beta 2 to beta 3 over Target Disk Mode, but would like to know if it's possible to bypass the model check and update without a supported Mac.

 

[0403979]

Yes. I had previously used a supported Mac to update it from beta 2 to beta 3 over Target Disk Mode, but would like to know if it's possible to bypass the model check and update without a supported Mac.

Patch your system from the usb with the Software Update patch and make sure you have the developer profile because beta 4 hasn’t been released for the public yet.

 

[redheeler]

Patch your system from the usb with the Software Update patch and make sure you have the developer profile because beta 4 hasn’t been released for the public yet.

I did a vanilla install of Mojave and added the necessary kexts myself, meaning I didn't use any ready-made or automated patch. Was hoping for some DIY instructions on how to resolve the problem, but I can look into Software Update patch if it's available for Mojave and download separately.

 

[0403979]

I did a vanilla install of Mojave and added the necessary kexts myself, meaning I didn't use any ready-made or automated patch. Was hoping for some DIY instructions on how to resolve the problem, but I can look into Software Update patch if it's available for Mojave and download separately.

It’s part of the patch tool. You can probably use this patch from High Sierra but I haven’t tested it so don’t complain if it messes up your system.

 

[CregoryNootinger]

I am now having an issue where I fully charge my MacBook Pro, but when I open it after a charge it says what it did before I charged it. I downloaded an app that tells me amperage as well as charge and this is what it said:

Charge Percent: 34%
Current Charge: 4896 mAh
Max Charge: 4941 mAh

(I know you can do it with System Report but this is simpler in my opinion)

It is not giving me that issue now, but a restart fixes it. Is this an issue with the patch or is this just my MacBook Pro? I ran a diagnostics test by booting it up and pressing the "D" key and it said that there are no hardware issues, so I wonder if it is just a minor glitch with Mojave?

 

[jackluke]

I am now having an issue where I fully charge my MacBook Pro, but when I open it after a charge it says what it did before I charged it. I downloaded an app that tells me amperage as well as charge and this is what it said:

Charge Percent: 34%
Current Charge: 4896 mAh
Max Charge: 4941 mAh

(I know you can do it with System Report but this is simpler in my opinion)

It is not giving me that issue now, but a restart fixes it. Is this an issue with the patch or is this just my MacBook Pro? I ran a diagnostics test by booting it up and pressing the "D" key and it said that there are no hardware issues, so I wonder if it is just a minor glitch with Mojave?

I did had a similar issue in past, given that I after learned that it is not healthy to charge a lithium battery 100%, it could be or SMC issue so resetting should fix it, or inaccurate software measuring incompatible libraries with the current MacOS, or a faulty battery, or less-powered Magsafe charger.
I don't exclude that patching could alterate battery values (not physical but logical).

Anyway most probably is the software (Battery Health I guess) that needs an update to support current MacOS libraries.

edit:
I thought you were referring to the Amperage (mA) instead of mAh capacity, an inadvertence of mine but I confirm what I have written before.

 

[0403979]

@redheeler I found the software updates patch that can be downloaded manually from here. This file is made by dosdude1 and is stored on his server so it'll be updated when needed.

 

[Larsvonhier]

I did had a similar issue in past, given that I after learned that it is not healthy to charge a lithium battery 100%, it could be or SMC issue so resetting should fix it, or inaccurate software measuring incompatible libraries with the current MacOS, or a faulty battery, or less-powered Magsafe charger.
I don't exclude that patching could alterate battery values (not physical but logical).

Anyway most probably is the software (Battery Health I guess) that needs an update to support current MacOS libraries.

Underlying framework seems not to have changed as "Coconut Battery" still works in a non-updated (Mojave) version and reports valid values on various MacBooks here.