macOS 10.14 Mojave on Unsupported Macs Thread

[0403979]

@joelw135 Sorry this is a bit late, I was doing something else. Try this and let me know if it works. Drag items into the window to use them. Don't forget to run chmod +x on this script and use sudo when running the script.

Edit: Newer version here.
[doublepost=1540668475][/doublepost]

I know it worked, but on a newer post he re-wrote adding another /Payload/ folder as destination path for expanding packages, so to copy from that you need to re-add the /Payload/Payload/ as copy source path.

Not to be rude but your command changes are unnecessary.

 

[jackluke]

@joelw135 Sorry this is a bit late, I was doing something else. Try this and let me know if it works. Drag items into the window to use them. Don't forget to run chmod +x on this script and use sudo when running the script.
[doublepost=1540668475][/doublepost]
Not to be rude but your command changes are unnecessary.

I know, but if you can as also @ASentientBot suggested, you should try this booting from another (HS or Mojave or USB Installer) Volume and not directly from booting the current Mojave, because I guess not 100% of the files are overwritten in this way, even if it worked.

 

[joelw135]

@joelw135 Sorry this is a bit late, I was doing something else. Try this and let me know if it works. Drag items into the window to use them. Don't forget to run chmod +x on this script and use sudo when running the script.
[doublepost=1540668475][/doublepost]
Not to be rude but your command changes are unnecessary.

How do I run it? I clicked it opened, but nothing ran.
Do I drag it to terminal? I tried that access denied.

 

[0403979]

How do I run it? I clicked it opened, but nothing ran.
Do I drag it to terminal?

Type chmod +x and drag the script, then type sudo and drag it again, then execute. Btw, there's a small spelling mistake in the first one. Here's a fixed version. I'm testing it now too.

Edit: Newer version here.

 

[joelw135]

I typed chmod +x in terminal then dragged the script then typed sudo and dragged again got access denied.

 

[WarHeadz]

Shot in the dark here, but I have a black MacBook with a Core Duo processor, is it possible to hack it to run anything above snow leopard?

 

[0403979]

Shot in the dark here, but I have a black MacBook with a Core Duo processor, is it possible to hack it to run anything above snow leopard?

Nope, period.
[doublepost=1540669059][/doublepost]

I typed chmod +x in terminal then dragged the script then typed sudo and dragged again got access denied.

Show me please. Also, there are visual issues with this, namely scrolling text. This will all be fixed soon.

 

[joelw135]

Type chmod +x and drag the script, then type sudo and drag it again, then execute. Btw, there's a small spelling mistake in the first one. Here's a fixed version. I'm testing it now too.

I now get Superuser permissions check failed
[doublepost=1540669359][/doublepost]

Nope, period.
[doublepost=1540669059][/doublepost]
Show me please. Also, there are visual issues with this, namely scrolling text. This will all be fixed soon.

 

[0403979]

I now get Superuser permissions check failed

You have to put sudo in front of the script path.

 

[joelw135]

You have to put sudo in front of the script path.

You have to put sudo in front of the script path.

What do I put for location look below?

 

[0403979]

What do I put for location look below?

The folder that has the package in it. Desktop I think in your case, go to your home folder, and drag it to the window.

 

[joelw135]

What do I put for location look below?

Do I restart as it hasn't restarted on it's own?

 

[0403979]

Do I restart as it hasn't restarted on it's own?

Type sudo reboot. This is an issue I've fixed now too.
[doublepost=1540669970][/doublepost]New patch update. This one should work flawlessly.

 

[joelw135]

Type sudo reboot. This is an issue I've fixed now too.
[doublepost=1540669970][/doublepost]New patch update. This one should work flawlessly.

When I reboot do I just reboot or got into patcher?

 

[0403979]

New patch update. This one should work flawlessly.

And I was wrong about that. Here's another juicy bug fix. The other should work for most people tho.
[doublepost=1540670253][/doublepost]

When I reboot do I just reboot or got into patcher?

Some people have said they didn't need it but I'd do it just to be sure.

 

[thegurgz]

And I was wrong about that. Here's another juicy bug fix. The other should work for most people tho.

Worked by using the terminal commands and adding the /Payload/ target at the end. Smart thinking to avoid the firmware update!!

 

[0403979]

Worked by using the terminal commands and adding the /Payload/ target at the end. Smart thinking to avoid the firmware update!!
View attachment 798793

I wouldn’t complicate it with @jackluke’a additions, my script and commands work fine. Of course if you find a bug with them, please let me know and I’ll help as soon as I can.

 

[thegurgz]

I wouldn’t complicate it with @jackluke’a additions, my script and commands work fine. Of course if you find a bug with them, please let me know and I’ll help as soon as I can.

I didn't use his additions of the other /Payload/ path, just the instructions you posted here. Worked smoothly, and a lot quicker than an update normally would take if going by the book.

 

[joelw135]

And I was wrong about that. Here's another juicy bug fix. The other should work for most people tho.
[doublepost=1540670253][/doublepost]
Some people have said they didn't need it but I'd do it just to be sure.

No luck, I must have done something wrong, but don't know what. When it says please respond with a path what do I do? Do I drag my Macintosh HD from Finder to the terminal?

 

[jackluke]

I didn't use his additions of the other /Payload/ path, just the instructions you posted here. Worked smoothly, and a lot quicker than an update normally would take if going by the book.

I did not add nothing, I only reported wrong syntax into destination/source paths. A lot quicker than regular update because it skips overwriting many core system files due to locked frameworks and processes aka unix core binaries on the booted Mojave. Even if it worked.

Every Apple official update is done through another mount point not on-the-fly to complete 100% the system core files overwriting.

 

[0403979]

I know it worked, but on a newer post he re-wrote adding another /Payload/ folder as destination path for expanding packages, so to copy from that need to re-add the /Payload/Payload/ as copy source path.

This was a mistake, don’t add that folder twice. Just don’t.

 

[jackluke]

This was a mistake, don’t add that folder twice. Just don’t.

I know, that was only a misunderstanding, I really don’t need to update, I can wait for 10.14.1 final release probably on October 30th.

 

[0403979]

I know, that was only a misunderstanding, I really don’t need to update, I can wait for 10.14.1 final release probably on October 30th.

I don’t think the final will remove the firmware update issues.

 

[jhowarth]

I don’t think the final will remove the firmware update issues.

However, as usual, the final update will be accompanied by a parallel update to the full installer for Mojave which will solve the installation issues.

 

[joelw135]

This was a mistake, don’t add that folder twice. Just don’t.

I gave up on the script and used the terminal commands and all is working. Chances are it was me not the script as I was confused with path etc. How about a full tutorial for others in the same boat.

My problems I think happened after the script asked for the file to update then the volume to update. I believe that is where my problems happened.