macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

Thanks for the help @jackluke Unfortunately this still did not work, I still can't get into recovery! I did get a final confirmation upon the updatePreboot command

"UpdatePreboot: Exiting Update Preboot operation with overall error=(ZeroMeansSuccess)=0"

And if this means anything, I do have a BOOTCAMP partition on the same drive, could this be interfering? This all makes no sense! Recovery would work using the -no_compat_check when installed on an HFS volume, but not APFS, I don't understand!

I don't think, I have Bootcamp too and 2 legacy OSXs and APFS Recovery works fine, then to discover what's behind the prohibitory symbol, from Mojave Terminal do this:

sudo nvram boot-args="-no_compat_check -v"
sudo reboot

at the chime, hit CMD+R and report a picture of what's happening.

You wrote that setting in nvram "kext-dev-mode=1" Recovery runs ? I use often to enforce invalid signatures on some machines but many wrote that is a deprecated argument.

 

[ASentientBot]

kext-dev-mode

It does nothing.

 

[jackluke]

It does nothing.

Right, they feel the same way: https://developer.apple.com/library..._Guide/KernelExtensions/KernelExtensions.html

 

[0403979]

so it is a common problem - how are guys doing on officially supported systems?
[doublepost=1552762978][/doublepost]
Not much to see.
As mentioned: Your and dosdude1´s patched installer behave identical on MB 5,2 - you can move mousepointer, but "unaccelerated", very slow. After the installation, it stays that way until the patch updater finds a "keyboard and trackpad patch" and you install it. This patch only shows up on the specific 5,2 machine, nowhere else.
After installation of that patch, you can use the trackpad as described at page #1ff. It will be seen by the system as a mouse, though.

Unfortunately, I can’t create a prelinkedkernel for the macbook4,1 myself. I don’t know the process you have used to create yours and so I’m kinda apprehensive to use it without the knowledge. I has to use @dosdude1 prelinkedkernels for Sierra and High Sierra since I only have the last installers. Out of interest, how did you (dosdude1) create the prelinkedkernels for Sierra and High Sierra? What files were replaced at rebuild time?

 

[jackluke]

Unfortunately, I can’t create a prelinkedkernel for the macbook4,1 myself. I don’t know the process you have used to create yours and so I’m kinda apprehensive to use it without the knowledge. I has to use @dosdude1 prelinkedkernels for Sierra and High Sierra since I only have the last installers. Out of interest, how did you (dosdude1) create the prelinkedkernels for Sierra and High Sierra? What files were replaced at rebuild time?

Agree, it's not so simple to create a "valid" prelinkedkernel for MB4,1 (or others) from a different hardware, I believe the best way to test is to have many kind of different machines and try the prelinkedkernel that best fits for all. Anyway you can issue a prelinkedkernel build after replaced the IOUSB* legacy kext (the only ones I believe really required to boot an OSX Installer) in S/L/E, chowning/chmoding their target Volume and lastly send: kextcache -system-prelinked-kernel /Volumes/YourLabel/

 

[DuncanGarp]

### post deleted

 

[Jas-Singh685]

I don't think, I have Bootcamp too and 2 legacy OSXs and APFS Recovery works fine, then to discover what's behind the prohibitory symbol, from Mojave Terminal do this:

sudo nvram boot-args="-no_compat_check -v"
sudo reboot

at the chime, hit CMD+R and report a picture of what's happening.

You wrote that setting in nvram "kext-dev-mode=1" Recovery runs ? I use often to enforce invalid signatures on some machines but many wrote that is a deprecated argument.

Okay so the recovery booted perfectly using this command! No errors or problems it loaded straight into recovery with the command lines showing.

However I tried the nvram -v command and it shows the platform is not supported! It seems like the -no_compat_check isn’t being recognised in the boot.plist? I’ve attached a photo of a normal verbose recovery boot. But again the command you posted worked just fine!

 

[DuncanGarp]

Has anyone installed macOS 10.14.5 public beta 5?

Yes I have. Installed on both a supported Macmini6,2 (late 2012) and unsupported MacBookAir4,2 (mid 2011). For the latter, I used @dosdude1's excellent patch updater app.

Any issues in your case?

 

[0403979]

Anyone noticed that on #1 the icon representing the supported MB 5,2 (and the 4,1 in disguise ;-) is missing?
I´ve prepared a scaled-down Mojave wallpaper version, but after several attempts to include it on page 1 at the right place I give up on this - perhaps someone else might try successfully?

View attachment 826022
Pic is attached above.
I would personally include it in the line of laptops, so that perhaps the MPro starts the third row?

Any chance you can find a better quality image?

 

[sadbuttrue]

If you just install over the previous OS without erasing it, all your files and settings should be safe.

There were a couple times when my account got downgraded to a non-admin user, and I had to fix that. But that seems to be a result of the manual installation, if you use dosdude1's patcher, you should not encounter this.

Anyone else have this issue of downgrading user accounts?

I am on 10.14.3, and performed a clean install, using @dosdude1 's installer. Everything was going great, but I have now discovered that my account has been downgraded to 'standard', so I can't install or do anything.

Any ideas, beyond flattening it and starting again? TIA

 

[ASentientBot]

Anyone else have this issue of downgrading user accounts?

I am on 10.14.3, and performed a clean install, using @dosdude1 's installer. Everything was going great, but I have now discovered that my account has been downgraded to 'standard', so I can't install or do anything.

Any ideas, beyond flattening it and starting again? TIA

Boot into single-user mode and run:

rm /var/db/.AppleSetupDone
exit

This'll relaunch the Setup Assistant and let you make another account. From there, you can set your old account as an administrator again.

 

[0403979]

Boot into single-user mode and run:

rm /var/db/.AppleSetupDone
exit

This'll relaunch the Setup Assistant and let you make another account. From there, you can set your old account as an administrator again.

Note: This works with FileVault too. You just need to unlock the volume first.

 

[jackluke]

Okay so the recovery booted perfectly using this command! No errors or problems it loaded straight into recovery with the command lines showing.

However I tried the nvram -v command and it shows the platform is not supported! It seems like the -no_compat_check isn’t being recognised in the boot.plist? I’ve attached a photo of a normal verbose recovery boot. But again the command you posted worked just fine!

It's a strange event in your picture (I assume when you don't set in nvram -no_compat_check), in general when pressing CMD+R the path of the "boot.efi" should be the Recovery one, instead in your case it's (again) the main Mojave Volume (S/L/CoreServices/). I don't know exactly why but I guess it's a mismatch and I think it will be auto-fixed by next update. As last attempt try to delete from this folder the bolded file:
/Volumes/Recovery/B75FA6B6-4DED-45CF-8642-6E40A48E2683/PlatformSupport.plist

edit:
One more attempt to re-align the APFS scheme from Mojave Terminal:
sudo diskutil apfs updatePreboot disk1s1

 

[FarmerBob]

Yes I have. Installed on both a supported Macmini6,2 (late 2012) and unsupported MacBookAir4,2 (mid 2011). For the latter, I used @dosdude1's excellent patch updater app.

Any issues in your case?

What all did you do? A step by step would be greatly appreciate! Thx.

Things are totally stuck during start up.
[doublepost=1552823014][/doublepost]

That's because of the graphics acceleration issues... Apply the patch I posted above, and that will fix your issue (you can boot Safe Mode to do so).

Can't get into "Safe Mode" I just get the greyed out "Circle Bar" symbol. Can get to Single User, but have no idea what to do from there. I'm no stranger to using this avenue, but I can't get to the dir with the files. Anything else I get it to the frozen white whirlygig. AND now that 14.5 is out, do we need to do anything special with that or will all the instructions for 14.4 work?

TIA!!

 

[jackluke]

What all did you do? A step by step would be greatly appreciate! Thx.

Things are totally stuck during start up.
[doublepost=1552823014][/doublepost]

Can't get into "Safe Mode" I just get the greyed out "Circle Bar" symbol. Can get to Single User, but have not idea what to do from there. I can't get to the dir with the files. Anything else I get it to book to the frozen white ring. AND now that 14.5 is out, do we need to do anything special with that.

TIA!!

To try force entering into "safe mode" try this from single user moder (CMD+S) typing exacly as is:

nvram boot-args="-no_compat_check -x -v"
reboot

to exit from safe mode hold after power on chime CMD+ALT+P+R or re-enter CMD+S typing:
nvram boot-args="-no_compat_check"
reboot

 

[Larsvonhier]

Any chance you can find a better quality image?

What do you expect, it is scaled down to the mini-size that is displayed at page #1 - only difference is that the alpha channel (background opacity) is not included. Should not matter on white background anyway.
[doublepost=1552828086][/doublepost]

@Larsvonhier

This shows the existence of the partial fixer patch for trackpad... (on MB5,2).
It shows up on the MB 4,1 as well, but does not work there on its own without the USB legacy 4,1 patches...
[doublepost=1552828322][/doublepost]

Unfortunately, I can’t create a prelinkedkernel for the macbook4,1 myself. I don’t know the process you have used to create yours and so I’m kinda apprehensive to use it without the knowledge. I has to use @dosdude1 prelinkedkernels for Sierra and High Sierra since I only have the last installers. Out of interest, how did you (dosdude1) create the prelinkedkernels for Sierra and High Sierra? What files were replaced at rebuild time?

The problem with the prelinked 4,1 kernel will hopefully be resolved within the next few weeks ;-)
Until then, I will be happy to provide kernels from my MB4,1 machine, if needed.

 

[0403979]

What do you expect, it is scaled down to the mini-size that is displayed at page #1 - only difference is that the alpha channel (background opacity) is not included. Should not matter on white background anyway.
[doublepost=1552828086][/doublepost]
This shows the existence of the partial fixer patch for trackpad... (on MB5,2).
It shows up on the MB 4,1 as well, but does not work there on its own without the USB legacy 4,1 patches...
[doublepost=1552828322][/doublepost]
The problem with the prelinked 4,1 kernel will hopefully be resolved within the next few weeks ;-)
Until then, I will be happy to provide kernels from my MB4,1 machine, if needed.

The image should be fine on a white background. Too bad I have a dark theme. I've included the trackpad patch in my patcher now. I use a specific process to create prelinkedkernels that involves replacing as little drivers as possible since the installer only needs a few. I would really like to know how @dosdude1 creates his and what files he replaces since I have had to use his due to a lack of installers. I could go through this process with you if you have a 10.14.0 installer. I'd rather take the approach dosdude1 has with the MB4,1. That is to say that we only create a new prelinkedkernel every time it's needed and not just for every version.

 

[jklas]

The MacBookPro4,1 has an Intel chipset, NOT an nVidia MCP79. Those are the machines that my tool has issues flashing.

Hello dosdude1,

First of all I want to thank you in advance for helping me and for doing such a great job for all others here.

I got a MBP 8,2 with the graphic issue. But it has A Intel HD 3000 card. I used the tutorial to fix it from AppleMacFinder and Mike. It worked then in the end. I could write that /force_i_GPU_LooginHook.sh and worked properly for me. Anyway I wanted to use Mojave. Unfortunately I did a big stupid mistake from my side... . I didn’t do a Backup dunno why but I didn’t... . Anyway. I could install over my High Sierra the Mojave upgrade from your USB-Stick Version. I ran the Patch and then the loading screen is just frozen. So it doesn’t boot at all. I ran the Patcher once more. And so on... . Anyway. I tried the last command here from the nvram and checkup. Then the Loading screen was half full and also moved! BUT JUST till 3/4 and then again reboots. This is repeating all over again. My SSD still has the same Data-amount on it and also it is APFS converted from your upgrading.

So could you maybe help me and tell me how to fix this/what to do to use the Mac again. And basically I don’t wanna lose my data. I know that I can take out the SSD and then put it on a external SSD-Drive to get get the data. But I would like to just get on the fly working.

And advices And help would be great.
Thanks to everybody.

Best Regards,

Jklas

P.S.: I tried the /force script to boot the display normal and worked but was stucked also. And I tried to do it manually with the nvram values. And I tried to let it get fixed by your post patcher!

 

[Jas-Singh685]

It's a strange event in your picture (I assume when you don't set in nvram -no_compat_check), in general when pressing CMD+R the path of the "boot.efi" should be the Recovery one, instead in your case it's (again) the main Mojave Volume (S/L/CoreServices/). I don't know exactly why but I guess it's a mismatch and I think it will be auto-fixed by next update. As last attempt try to delete from this folder the bolded file:
/Volumes/Recovery/B75FA6B6-4DED-45CF-8642-6E40A48E2683/PlatformSupport.plist

edit:
One more attempt to re-align the APFS scheme from Mojave Terminal:
sudo diskutil apfs updatePreboot disk1s1

Yes that is correct, the picture was only nvram -v, not no_compat_check. I tried deleting the file you mentioned and it's still not working. I can see what you mean by the boot.efi being loaded from the wrong volume, I guess there is no way to change the path so it's to the recovery volume instead?

I guess for now I can just use the nvram -no_compat_check in the meantime until there is an update? At least I can load recovery that way. I don't need to reset the PRAM often anyway! Thanks for all the help @jackluke

 

[jklas]

To try force entering into "safe mode" try this from single user moder (CMD+S) typing exacly as is:

nvram boot-args="-no_compat_check -x -v"
reboot

to exit from safe mode hold after power on chime CMD+ALT+P+R or re-enter CMD+S typing:
nvram boot-args="-no_compat_check"
reboot

Hey jackluke,

the first command try fixed my issue in the first place. It bootet and writes that it is a safe boot mode. I gonna give it a try with the safe mode exit. I hope that it will fix my issue at all.
Thanks first of all in the first place!

Best Regards,

jklas

EDIT: After trying the second command to get out of the safe mode. It get stucks again after 75% of boot screen bar.
So it worked and showed me the first time my mojave and my user and I could login my self...in the safe mode but not after typing the second command again.. ..
Any suggestions?

Thans

 

[Macschrauber]

About the Recovery Partition: Simply copy PlatformSupport.plist from patched Mojave to the Recovery. Survives even a NVRam reset.

Did that just recently with two Mac Pro 3.1 in 10.14.3 APFS and HFS.

APFS was a little odd, the Files were in a long numbered Folder instead of the root dir.

 

[Athanti]

hello
I used these commands:
diskutil mount disk1s3
diskutil apfs changeVolumeRole disk1s3 R
diskutil apfs updatePreboot disk1s1

sudo reboot
to get in recovery on mbp 8.2 and everything worked right. it boots into Recovery.
But every time I boot it starts in verbose mode.
How to stop this?

 

[Jas-Singh685]

About the Recovery Partition: Simpy copy PlatformSupport.plist from patched Mojave to the Recovery. Survives even a NVRam reset.

Did that just recently with two Mac Pro 3.1 in 10.14.3 APFS and HFS.

APFS was a little odd, the Files were in a long numbered Folder instead of the root dir.

Just tried this too, I noticed the additional supported devices in the file, but still no luck!

 

[jackluke]

Yes that is correct, the picture was only nvram -v, not no_compat_check. I tried deleting the file you mentioned and it's still not working. I can see what you mean by the boot.efi being loaded from the wrong volume, I guess there is no way to change the path so it's to the recovery volume instead?

I guess for now I can just use the nvram -no_compat_check in the meantime until there is an update? At least I can load recovery that way. I don't need to reset the PRAM often anyway! Thanks for all the help @jackluke

Apart "diskutil apfs updatepreboot /" I don't know another way how to set the right boot.efi to the correct APFS Volume, the fact you had two folders inside your /Volumes/Recovery means that something got wrong in past, but I think a next update could correct that. Meanwhile nvram parameters win over everything, so not a big issue.
[doublepost=1552841207][/doublepost]

hello
I used these commands:
diskutil mount disk1s3
diskutil apfs changeVolumeRole disk1s3 R
diskutil apfs updatePreboot disk1s1

sudo reboot
to get in recovery on mbp 8.2 and everything worked right. it boots into Recovery.
But every time I boot it starts in verbose mode.
How to stop this?

Simply from Mojave Terminal: sudo nvram boot-args="-no_compat_check"
[doublepost=1552841452][/doublepost]

Hey jackluke,

the first command try fixed my issue in the first place. It bootet and writes that it is a safe boot mode. I gonna give it a try with the safe mode exit. I hope that it will fix my issue at all.
Thanks first of all in the first place!

Best Regards,

jklas

EDIT: After trying the second command to get out of the safe mode. It get stucks again after 75% of boot screen bar.
So it worked and showed me the first time my mojave and my user and I could login my self...in the safe mode but not after typing the second command again.. ..
Any suggestions?

Thans

The fact you can reach the GUI Mode in safe-mode means that some graphics kext to gain OpenGL or CoreBrightness or maybe other kext are incorrect. If you are on 10.14.4 you should apply from the safe mode the dosdude1 accelpatch, if you are on 10.14.3 or lower I think you should re-apply the dosdude1's Post Install Video patch, and from there force rebuild cache.

 

[Jas-Singh685]

Apart "diskutil apfs updatepreboot /" I don't know another way how to set the right boot.efi to the correct APFS Volume, the fact you had two folders inside your /Volumes/Recovery means that something got wrong in past, but I think a next update could correct that. Meanwhile nvram parameters win over everything, so not a big issue.

I did upgrade directly from High Sierra, do you think it's worth wiping the partition and trying again with a clean install? (Leaving my Bootcamp partition untouched)