macOS 10.14 Mojave on Unsupported Macs Thread

[MacUnsupported]

Mr @dosdude1 when you will probably create the final patch ?

Last one I tried doesn’t work . You are an amazing developer!
iMac 2009 frozen screen on apple bar and finally shut down !
I m very sad my machine can’t work right now because I
Have no time machine

 

[webg3]

Mr @dosdude1 when you will probably create the final patch ?

Last one I tried doesn’t work . You are an amazing developer!
iMac 2009 frozen wceeen on apple bar and finally shut down !

Try other patch: 1.2.0 working for me

 

[MacUnsupported]

Try other patch: 1.2.0 working for me

I got iMac 2009 late what’s your model ? 10.1? Cheers

 

[lukiy]

I think exactly the same way, just take a look at Insanelymac, tonymac86 and other followings. You do not see the source code of the tools scattered around, just the utility itself that has GUI to facilitate.

The content of the patch needs to be open sourced and peer reviewed to avoid any future catastrophes and troubles for @dosdude1. Just imagine the case of an honest mistake where @dosdude1 may add a line in the patch that adds a rogue behavior to the patch.

Users need to understand that the patches ask for admin password, they can do anything beside the patching.

Another problem for @dosdude1 could be a legal one. There is no privacy terms and conditions for this software. We do not know if the patcher software collects any data, including personal data on the local disk, from users. At least, when it comes to EU and GDPR, that can put @dosdude1 in some serious trouble.

I understand that this is to help people on unsupported Apple hardware, but that does not mean that this software can be treated like some pirated software. Links to download and instructions are being distributed via macrumors.com, and that can put them into legal troubles too. So if something goes wrong, consider threads like this to be removed.

All these can be resolved by open sourcing the patches. In fact, by open sourcing, we can use the effort of the open source community to tackle unresolved problems like transparency. Surely there are people in the open source community that would be happy to help. But the current setup makes this impossible.

 

[Vegerot]

the "apfs_stop_bg_work" occurs on any reboot or shutdown if you booted Mojave in verbose mode, I would say it's normal apfs routine, I do have many of these instances since Mojave beta 1, nothing to worry about.

Would you clarify that? Are you saying that that only happens when you're in verbose boot, as in there is some difference (beyond logs) between regular and verbose boot?

 

[miguelromm]

A simple doubt: What is the "Recovery Partition Patch" for? To mantain macOS recovery functional when the user update macOS?

Thank you.

 

[webg3]

The content of the patch needs to be open sourced and peer reviewed to avoid any future catastrophes and troubles for @dosdude1. Just imagine the case of an honest mistake where @dosdude1 may add a line in the patch that adds a rogue behavior to the patch.

Users need to understand that the patches ask for admin password, they can do anything beside the patching.

Another problem for @dosdude1 could be a legal one. There is no privacy terms and conditions for this software. We do not know if the patcher software collects any data, including personal data on the local disk, from users. At least, when it comes to EU and GDPR, that can put @dosdude1 in some serious trouble.

I understand that this is to help people on unsupported Apple hardware, but that does not mean that this software can be treated like some pirated software. Links to download and instructions are being distributed via macrumors.com, and that can put them into legal troubles too. So if something goes wrong, consider threads like this to be removed.

All these can be resolved by open sourcing the patches. In fact, by open sourcing, we can use the effort of the open source community to tackle unresolved problems like transparency. Surely there are people in the open source community that would be happy to help. But the current setup makes this impossible.

Oh My God, brother.

It's his software.

If he thinks he should, then he will share his source code.

Who are we to impose something?

Your opinion like that of many is wrong, but it is your opinion.

Just like mine, and others here, understand that his work can be stolen.

just take a look at the XDA community (Android source code) for example, that occurs a lot this, people taking credit for something they did not create.

The only thing he needs to do is document what's being used in the patch, just that, and that's what he's already stated to do.

Excuse me if I was coarse or rude, but I do not see where to go in this discussion, it's already a bit saturated.

My sincere apologies.

 

[Luckygreek]

Oh My God, brow.

It's his software.

If he thinks he should, then he will share his source code.

Who are we to impose something?

Your opinion like that of many is wrong, but it is your opinion.

Just like mine, and others here, understand that his work can be stolen.

just take a look at the XDA community (Android source code) for example, that occurs a lot this, people taking credit for something they did not create.

The only thing he needs to do is document what's being used in the patch, just that, and that's what he's already stated to do.

Excuse me if I was rude or rude, but I do not see where to go in this discussion, it's already a bit saturated.

My sincere apologies.

Well said webg3, no one is forcing anyone to use his patch & it's his choice whether or not to open source his software. Buy a new Mac if you have concerns about @dosdude1 patch. Personally I have no reservations about it.

 

[lukiy]

Oh My God, brow.

It's his software.

If he thinks he should, then he will share his source code.

Who are we to impose something?

Your opinion like that of many is wrong, but it is your opinion.

Just like mine, and others here, understand that his work can be stolen.

just take a look at the XDA community (Android source code) for example, that occurs a lot this, people taking credit for something they did not create.

The only thing he needs to do is document what's being used in the patch, just that, and that's what he's already stated to do.

Excuse me if I was rude or rude, but I do not see where to go in this discussion, it's already a bit saturated.

My sincere apologies.

I'm sorry, I did not mean that he does not own his software, or that we can force him to open source it. I did not mean any of that. I'm simply saying that there is a lot of risk involved here both for users, and the author(s) of the patches, when it comes to patching an OS.

As with stealing his work when it's open sourced, that makes no sense. There are millions of open source projects on the internet, none of the authors have lost their credit.

As with @dosdude1 being worried that other people might misuse his work and provide fake patches, again, there are millions of open source software out there that do not have same problem. All he has to do is to put the software on free github release page for everyone to download. That is much more secure than the random google drive links that are shared here.

I am sorry if sounded aggressive, that was not what I meant. It seems like the community here is not very familiar with how open source works.

 

[Starplayr]

The video card specs are:
Chipset Model: AMD Radeon HD 7950
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Dynamic, Max): 3072 MB
Vendor: AMD (0x1002)
Device ID: 0x679a
Revision ID: 0x0000
ROM Revision: 113-E2080C-101
VBIOS Version: 113-C3810100-U01
EFI Driver Version: 01.00.624
Metal: Supported, feature set macOS GPUFamily2 v1

Failed Mojave installer attempts gave the message "installer resources could not be located" with different downloaded Mojave installers, both on upgrades to HS 10.13.6 and fresh installs to ssd.

Try installing from the patcher instead. There are probably kinks in Apple’s implementation.

 

[joelw135]

Oh My God, brother.

It's his software.

If he thinks he should, then he will share his source code.

Who are we to impose something?

I agree, never make it open source as then we will never know who does what to it.

 

[whaffle]

Is graphic card switching on MBPs with nVidia 9400M and 9600 working?

 

[Starplayr]

I think exactly the same way, just take a look at Insanelymac, tonymac86 and other followings. You do not see the source code of the tools scattered around, just the utility itself that has GUI to facilitate.

Only difference is those are hackintosh sites. We are trying to get more years out of the Macs we bought. It would be great if it was open source but again, it doesn't need to be. It does enough getting most users headed in the right direction with Mojave. It does well with my 2009 Mac Book Pro and super well with my 2008 Mac Pros. Only issues really are some incompatible video cards with some MacBooks and iMacs which may be solved by replacing them, using miniPCIe or Thunderbolt eGPUs. I read that if USB is not connected to miniPCIe slot on the host, that it makes eGPUs useless. Many laptops are like this. So that leaves replacing compatible GPUs, waiting for Web Drivers for newer Nvidia Cards, and Thunderbolt eGPUs which aren't cheap compared to buying a fully capable used Mac Pro and you can run much better displays than the iMacs offer.

I am a little torn between getting an eGPU (enclosure) for my iMac or just sell it as is and put that towards other hardware. I have a couple great video card candidates for the eGPU but not sure how much of a bitch it is gonna be getting it to work on an unsupported Mac. Mac Pros are just easier to deal with in general and a 4,1 or 5,1 would be a nice upgrade. and supported MacBook Pros are gonna be easy peasy.

Already selling off a 2012 Mac mini. Just got tired of it. Mostly because Apple would not unlock the 4k scaled resolutions for it. And my 2008 Mac Pro has tons of 4k res' to choose from.

 

[webg3]

I got iMac 2009 late what’s your model ? 10.1? Cheers

MacBookPro7,1

 

[Starplayr]

@dosdude1 Is there a Night Shift patch for Mojave already?

Just a question, no demand!

Thanks.

Oh, as a side note: I successfully patched a Mac Pro 3.1 with the APFS ROM. Worked smoothly, I really appreciate this effort.

This machine runs wonderfully fast for its age, a self-knitted fusion drive (256GB SSD and 2TB HD) and an NVIDIA GeForce 680 GTX helps a lot with this.

But I'm surprised every day, what this machine is able to perform, if current and compatible software allows this!

It will run all the Adobe software. It will run Xcode. The only software it can't run out of the box is SSE4.1 and higher and so far its just a couple of things that Mojave uses for AMD and the Telemetry User Event plugin, so it's not a big deal right now. But if Apple move forward with SSE4.1 down the road, then an emulator will need to placed in the Kernel.

And since you have Metal, that's big deal really.

 

[PBear.SF]

Agreed, it was in apps folder & that's where it remains. High Sierra was exactly the same in terms of where App Store determines where to download OS's. Perhaps in some circumstances moving OS to another folder is a workaround.

Do you think it could be a SIP enabled/disabled issue? Perhaps if SIP is enabled the patcher is blocked from accessing the installer file if it's in the Applications folder.

Edit: Have since read that someone fixed the problem by resetting his PRAM, so who knows?

 

[ASentientBot]

To those arguing about open source, sorry for starting a fight. In my opinion, the distinction is simple.
--> Documentation is vital. What are we patching, and if we were to do it manually, how would we do that?
--> Open source is great, but not necessary. That is up to the author of the software.

For example, how to patch Night Shift is documented here. That is fantastic! There is no reason for dosdude1 to release the code for his automated Night Shift patcher if he doesn't want to. Any of us can write our own, now that the knowledge is public.

Another example is the nVidia Tesla patch. I explained that in detail here. That's all we need, really.

The problematic cases are things like the APFS Boot ROM patcher, SUVMMFaker.dylib, or LegacyUSBInjector. We neither know how those work, nor have the source code. This, in my opinion, needs to be fixed if possible.

 

[lukiy]

To those arguing about open source, sorry for starting a fight. In my opinion, the distinction is simple.
--> Documentation is vital. What are we patching, and if we were to do it manually, how would we do that?
--> Open source is great, but not necessary. That is up to the author of the software.

For example, how to patch Night Shift is documented here. That is fantastic! There is no reason for dosdude1 to release the code for his automated Night Shift patcher if he doesn't want to. Any of us can write our own, now that the knowledge is public.

Another example is the nVidia Tesla patch. I explained that in detail here. That's all we need, really.

The problematic cases are things like the APFS Boot ROM patcher, SUVMMFaker.dylib, or LegacyUSBInjector. We neither know how those work, nor have the source code. This, in my opinion, needs to be fixed if possible.

How about the servers that patches are download from? What if they get compromised? All of us here will get patches that can be really really dangerous. For example, they can upload our home directories etc.

I think you guys are really underestimating the security measures here.

 

[BookEmDanno]

I'm about to upgrade my unsupported MBP5,5 from 10.14 final release to 10.14.1 beta 1. Couple of questions please @pkouame.
Assuming I will receive OTA message from System Preferences | Software Update, download and reboot and post install.

1. Reset my boot-args on nvram ?
2. Do I need to SMC + PRAM reset ?

Thank You.

Also, on the post install, make sure to NOT click on the APFS selection?

@pkouame, I have the same questions as well. I have a MacBookPro5,3, similar to your post,

https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-323#post-26583546

and wanted to upgrade from 10.14 final release to 10.14.1 beta 1. There is an upgrade to Xcode 10.1 beta that I need to be able to download and install (which I think I won't be able to if I do not have 10.4.1 beta 1).

~Mahalo~!

 

[Starplayr]

You need to boot from the patched USB installer, NOT run the "Install macOS Mojave" app.

Ditto

 

[Aletancredo]

Hello, I am running macos mojave 10.14 GM, and I would like to try the version 10.14.1 beta 1.
I downloaded the dude patcher 1.22.
Could you help me how to do it?
My mac is a macbook pro 8,1. I tried by software update but it is not working.

Thank you very much.

 

[webg3]

Guys, I created a script for those who prefer to use only DarkMode (not to use in conjunction with LightMode), it is more pleasant this, because I put that code that smoothes the display fonts.

Enjoy.

 

[oscarodas]

Managed to install 10.14.1 after downloading the upgrade the system restarted and started to install but at about 3/4 progress bar it would stop, I tried a few times without change, then decided to use usb installer and started the installation, the apple logo turned yellow like in the old days of 16 colour graphics, when the installation finished it reboot and got back to normal, everything is ok.

 

[webg3]

defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO

This code broke something important concerning the imposition of gray color even in dark mode.

Look at the menus of applications that have no dark mode.

@jackluke / @pkouame this may be interesting for you.

 

[pkouame]

We may think that Apple will further modify the system so that unsupported macs are getting more and more distant, but it still supports some 2010 models, so as long as it keeps those models, we will be grateful.

Apple has much bigger fish to fry than us right now. No conspiracies - we're just neglected and have to fend for ourselves.
That's why the more people get in on this game and actually read and learn to test, diagnose, fix and patch themselves the better. This will become more challenging in the future (as core frameworks phase out of support)