macOS 10.14 Mojave on Unsupported Macs Thread

[pkouame]

One more thing that not many know about the 2018 mbp is that the vcore voltage modules for the cpu are under specced, they can not handle the current that the cpu needs. Its not just thermally. Sending out a firmware update does not fix that, its like the antennagate 4s iPhone.

When the modules go bad they send the battery voltage (12v) to the cpu and fries it.

I doubt that for someone that uses the 2018 mbp heavily and a lot that they would last 3 years.

Yup and Geez!

I've been following the throttling threads religiously and the famous reddit one... And it's sad.
They rushed the model out to meet Wall Street expectations - the thin enclosure can no longer cut it, the core i9 is dumbed down even though the throttling issues were kind of solved (but you're right not completely)

Haven't checked in a while, have they solved the bootcamp throttling issues? Not that I use bootcamp (nor would I recommend it, Apple does not support it well - a headache) - I'm strictly a VM guy (that's why I need a lap with at least 32GB)
[doublepost=1534965663][/doublepost]

That's what happened on my iMac, but it rebooted without no-entry screen, granted my wifi and later sound had to be patched but those were the only patches I ran and no trails. 18A371a

Edit; the only reason I knew was because I had no wifi or sound, checked about this Mac and noticed that 18A371a was my OS, I was on 18A365a

So I was keeping my mbp 5.3 at 6 just to test the jump to 8. Smooth. Expect for a slight glitch when I was hoping to catch the restart to option directly into post-install without having to shut down. I selected my patcher disk from the list of boot volumes and quickly jumped to no-entry. First time I see that. Had to shutdown hard and start. May be just a glitch, but skipping a beta version works well also...

 

[0403979]

There you go

I wanted my colours inverted like in that screenshot.

 

[TimothyR734]

I wanted my colours inverted like in that screenshot.

you can download the screen shot then set it as desktop wallpaper then go to accessabilty and invert the colors

 

[flygbuss]

Oh, I'm seriously getting into clover and hackintosh. I can build a screamer of a core i9 that will blow away anything Apple offers right now. I was about to take the big gulp for a 32GB 1TB SSD core i9 macbook pro (cause I need it for work) when the **** hit the fan on throttling issues, heat dissipation issues, bad keyboard, T2 crashing, SSD hardware encrypted, no upgrade path etc.
I can't see myself forking over that kind of cash for unstable machines anymore - at least until they fix their quality control processes. Sad. We've been waiting almost 6 years for a macpro...and all we get is a 1K mac mini...the writing is on the wall...

Thought about it as well and went for a small nMP 4C with the D500 which I upgraded to 2TB SSD, 32GB RAM and 10C CPU instead. A lot of moaning about these machines is out there as well but i work in audio production and for that the machine works quite well (Silent!). Since I bought it really cheap and did all the upgrades myself I didn't pay that much.

I also have a cMP 5,1 in the studio which I use for work but the lack of TB (a lot of good audio gear comes with TB) always bugged me. At least USB 3.1 gen. 2 works pretty good.

 

[dosdude1]

Did anyone had an inverted colors issue? Not inverted image, only colors. Luminosity its ok. I was trying Mojave on my iMac Late 2009 i7 but with a Radeon 6970m 2gb from a Alienware that was flashed with EFI to have boot screen.

The issue is present on both light and dark modes.

Here is the example: one is how it should looks and the weird is how it looks on Mojave.

Also performance in general it's not good, but I had to say that I was testing it from an old 80gb Toshiba HDD from and old 2006 Macbook.

View attachment 777296 View attachment 777295

You're having that issue because Radeon HD 5xxx and 6xxx series GPUs don't work properly under Mojave, as stated in the OP.

 

[TimothyR734]

I wanted my colours inverted like in that screenshot.

this is as red as I could get it

 

[guillepunx]

You're having that issue because Radeon HD 5xxx and 6xxx series GPUs don't work properly under Mojave, as stated in the OP.

Ok thanks! I was not sure as you didn't mentioned this particular issue and couldn't find someone talking about the same glitch. I just wanted to leave the example.

I hope when people start to work on kext for Mojave we can solve this.
[doublepost=1534970718][/doublepost]

I wanted my colours inverted like in that screenshot.

I can change you my late 2009 iMac for a new one if you wish

 

[Vyzantion]

Oh, I'm seriously getting into clover and hackintosh. I can build a screamer of a core i9 that will blow away anything Apple offers right now. I was about to take the big gulp for a 32GB 1TB SSD core i9 macbook pro (cause I need it for work) when the **** hit the fan on throttling issues, heat dissipation issues, bad keyboard, T2 crashing, SSD hardware encrypted, no upgrade path etc.
I can't see myself forking over that kind of cash for unstable machines anymore - at least until they fix their quality control processes. Sad. We've been waiting almost 6 years for a macpro...and all we get is a 1K mac mini...the writing is on the wall...

Go for it. But my advice is to try on a desktop Hackintoshing first, then a laptop. To get some experience, it is easier, as I said. Hackintoshing means a lot of technical issues, much more then running macOS on an unsupported Mac. If you decide to build a Hackintosh, build it, if possible, with the newest and best components, and make sure it is upgradable. Apple tolerates hackintoshing, they even want it, at a low rate, for user base, like Slice, the main developer of Clover, said. He also said that Apple could destroy Hackintoshing really quick, by banning FakeSMC. But they do not. Tonymacx86 is a certified Apple developer. But also Apple keeps hackintoshing to be really hard, in order to make some users decide to actually buy a Mac, in order to keep it easy, but also to make macOS like some sort of forbidden fruit, so people want it more.
[doublepost=1534972033][/doublepost]Would you, sorry if this was asked before, that Dark Mode, especially with Reduce Transparency and Dynamic Desktop off, that it loads faster and uses less resources the Light Mode?
My machine has serious issues on Mojave, on summer heat, on shut down, it often just blocks when it was suppose to turn off, after CPU Halted. This issues was on High Sierra, but much less often. DDST patching was a proposed solution, but that is beyond my current expertise.
Since Yosemite, first OS used on daily basis by me to High Sierra, login screen was grey. Now, it has the wallpaper. Perhaps something was enabled by the Dosdude1 patch that now needs more resources.

 

[TheSkywalker77]

Question: If I were to install it could I delete the files used to install it on my flash drive once it’s installed, and if I need the files again for anything could I redownload the tool and re-patch the files on the flash drive and use it again if I need it?

 

[Macschrauber]

You're having that issue because Radeon HD 5xxx and 6xxx series GPUs don't work properly under Mojave, as stated in the OP.

and (as my latest investigations) you had the legacy video patch enabled. So re-install without legacy video patch - and check if you got 30 bit colours (what gives you false colours). Those Billion colours can be fixed with a tool like ResXtreme http://resxtreme.com

should be at the 1st page: don't set the legacy video patch if you have a HD5xxx or HD6xxx GPU - you get GUI glitches. Also you get no OpenGL - but anyway the mac is usable - if it's usable enough, one must find out for his own needs.

 

[the.burn]

Hey
So, I followed this thread for quite a time and today I could not wait any longer to try Mojave on my MBP 2010 15" (6,2)...
Unfortunately, I'm out of luck, installation was running infinitely

My setup: MacBook Pro 2010 15"
USB Stick: 16GB, Patched Installed seemed to be copied on it successful, as "macOS Mojave Patcher" said at the end.
Destination for Mojave: Old internal HDD, now connected through a USB-to-SATA interface (ICY Box). Formatted for a clean install (MacOS Extended Journaled, GUID table)

After starting the installation on this HDD, the progress bar increased for maybe 1-5 minutes, stating that the installation will take about 16min...
However, after some minutes the bar did not increase anymore. I waited for more than an hour, but no progress, still 16minutes left.

I would be glad if sb can help me identifying the issue, as I copied the installation log.
(Attached versions are only errors and warning, and complete log)

Any help is appreciated )
Thank you sooo much for all the effort you already invested!

 

[0403979]

Question: If I were to install it could I delete the files used to install it on my flash drive once it’s installed, and if I need the files again for anything could I redownload the tool and re-patch the files on the flash drive and use it again if I need it?

Yes you can. The drive is only for installation and patching after updates. You do not need to have the drive once you have Mojave installed and patched but I would keep it anyway in case something goes wrong because normal recovery won’t work on unsupported devices.

 

[TimothyR734]

,

Hey
So, I followed this thread for quite a time and today I could not wait any longer to try Mojave on my MBP 2010 15" (6,2)...
Unfortunately, I'm out of luck, installation was running infinitely

My setup: MacBook Pro 2010 15"
USB Stick: 16GB, Patched Installed seemed to be copied on it successful, as "macOS Mojave Patcher" said at the end.
Destination for Mojave: Old internal HDD, now connected through a USB-to-SATA interface (ICY Box). Formatted for a clean install (MacOS Extended Journaled, GUID table)

After starting the installation on this HDD, the progress bar increased for maybe 1-5 minutes, stating that the installation will take about 16min...
However, after some minutes the bar did not increase anymore. I waited for more than an hour, but no progress, still 16minutes left.

I would be glad if sb can help me identifying the issue, as I copied the installation log.
(Attached versions are only errors and warning, and complete log)

Any help is appreciated )
Thank you sooo much for all the effort you already invested!

I suggest reformat you hdd macOS extended journaled and name your hdd something like macOS hdd instead of untitled that could be the issue

 

[TheSkywalker77]

Yes you can. The drive is only for installation and patching after updates. You do not need to have the drive once you have Mojave installed and patched but I would keep it anyway in case something goes wrong because normal recovery won’t work on unsupported devices.

Yeah I understand regular recovery won’t work without it. But if I did delete it and something did go wrong I could just redownload the tool onto the drive and use it for recovery?

 

[Vyzantion]

,

I suggest reformat you hdd macOS extended journaled and name your hdd something like macOS hdd instead of untitled that could be the issue

Macintosh HD is the default name of the system partition. I use it even on my Hackintosh. Clover checks for default for a portion called MacHHD, to set it as automatic boot. The Tonymacx86 edit of Clover checks for the partition it is installed on, to get automatic boot.

 

[the.burn]

,

I suggest reformat you hdd macOS extended journaled and name your hdd something like macOS hdd instead of untitled that could be the issue

Ok thats strange indeed, as I named it „macOS Mojave“... It should not be untitled

 

[thegurgz]

,

I suggest reformat you hdd macOS extended journaled and name your hdd something like macOS hdd instead of untitled that could be the issue

No, the drive is not called 'untitled'. The installers runs checks on every disk in the SSD, and there are hidden disks named 'untitled' that are around 512mb or smaller. You can see this by running "diskutil list", you'll see all the untitled disks. The SSD had around 20 untitled disks. You can google what these disks do, I won't get into it.
[doublepost=1534978080][/doublepost]

Hey
So, I followed this thread for quite a time and today I could not wait any longer to try Mojave on my MBP 2010 15" (6,2)...
Unfortunately, I'm out of luck, installation was running infinitely

My setup: MacBook Pro 2010 15"
USB Stick: 16GB, Patched Installed seemed to be copied on it successful, as "macOS Mojave Patcher" said at the end.
Destination for Mojave: Old internal HDD, now connected through a USB-to-SATA interface (ICY Box). Formatted for a clean install (MacOS Extended Journaled, GUID table)

After starting the installation on this HDD, the progress bar increased for maybe 1-5 minutes, stating that the installation will take about 16min...
However, after some minutes the bar did not increase anymore. I waited for more than an hour, but no progress, still 16minutes left.

I would be glad if sb can help me identifying the issue, as I copied the installation log.
(Attached versions are only errors and warning, and complete log)

Any help is appreciated )
Thank you sooo much for all the effort you already invested!

There was an error in the installation that might have been the problem.

Aug 22 19:47:37 MacBook-Pro OSInstaller[573]: Not enough freespace on Mojave to do straight install.
Aug 22 19:47:37 MacBook-Pro OSInstaller[573]: Available: 8266743808
Aug 22 19:47:37 MacBook-Pro OSInstaller[573]: Required: 14000728064
Aug 22 19:47:37 MacBook-Pro OSInstaller[573]: Not enough space on target and nothing that looks like a system to reap.

This error is strange, since you said that it was a clean install. Try erasing and running again. I have not read too many install logs, however, so this could be a benign error. Someone correct me if I am wrong.
[doublepost=1534978298][/doublepost]Also, unrelated, but the log randomly started speaking in German a few times, then switched back in English. Never seen that before

Spoiler

Aug 22 19:52:27 MacBook-Pro OSInstaller[573]: Multi-Link-Dateien werden überprüft.
Aug 22 19:52:27 MacBook-Pro OSInstaller[573]: Kataloghierarchie wird überprüft.
Aug 22 19:52:27 MacBook-Pro OSInstaller[573]: Datei für erweiterte Attribute wird überprüft.
Aug 22 19:53:51 MacBook-Pro OSInstaller[573]: Volume-Bitmap wird überprüft.
Aug 22 19:54:00 MacBook-Pro OSInstaller[573]: Informationen des Volumes werden überprüft.
Aug 22 19:54:00 MacBook-Pro OSInstaller[573]: Das Volume „macOS Mojave“ ist anscheinend in Ordnung.

 

[Hughmac]

I wanted my colours inverted like in that screenshot.

Control + Option + Command + 8 inverts the colours, repeat to revert to normal

Cheers

Hugh

 

[guillepunx]

and (as my latest investigations) you had the legacy video patch enabled. So re-install without legacy video patch - and check if you got 30 bit colours (what gives you false colours). Those Billion colours can be fixed with a tool like ResXtreme http://resxtreme.com

should be at the 1st page: don't set the legacy video patch if you have a HD5xxx or HD6xxx GPU - you get GUI glitches. Also you get no OpenGL - but anyway the mac is usable - if it's usable enough, one must find out for his own needs.

So this is in fact the kind of answer I was spectating before. Was suspecting from Legacy Video Patch, but thought that didn't deserve the waste of time to try it. Some info about what exact do each patch should be great for deal with this kind of issues and test all better. Dont get me wrong, I'm very thankful for op works to be able to use Mojave in "old" machines.

Tomorrow I should try to use it without Legacy Video Patch. By the way, it's necessary to reinstall completely the os, or just necessary to run post install patcher and uncheck the one that you want to deactivate?

Thanks!

 

[the.burn]

@thegurgz
The „Mojave“ drive you cited from the log, which is said to be not large enough, is the USB install stick (16GB)...
The HDD is called „macOS Mojave“ and of I‘m seeing it correctly installation is started at this correct drive, while the other „error“ is just an information

FYI: Installation was completelly successful on a partion on my Firewire TimeMaschine drive...
So, I assume it has something to do with the HDD hardware?!

 

[thegurgz]

@thegurgz
The „Mojave“ drive you cited from the log, which is said to be not large enough, is the USB install stick (16GB)...
The HDD is called „macOS Mojave“ and of I‘m seeing it correctly installation is started at this correct drive, while the other „error“ is just an information

FYI: Installation was completelly successful on a partion on my Firewire TimeMaschine drive...
So, I assume it has something to do with the HDD hardware?!

Yeah, I just saw it was only for that disk but then I read you titled it macOS Mojave. What make/model for your HDD? My internal Hitachi HTS545025B9SA02 Media has Mojave running on it just fine. Was it an HFS+ drive or APFS? There has been issues with APFS installing on HDDs.

 

[the.burn]

Yeah, I just saw it was only for that disk but then I read you titled it macOS Mojave. What make/model for your HDD? My internal Hitachi HTS545025B9SA02 Media has Mojave running on it just fine. Was it an HFS+ drive or APFS? There has been issues with APFS installing on HDDs.

It‘s a Hitachi 500GB drive, currently I don‘t geht the full name
For that reason I‘ve chosen Mac OS Extended Journaled to avoid that kind of issues

 

[Macschrauber]

Tomorrow I should try to use it without Legacy Video Patch. By the way, it's necessary to reinstall completely the os, or just necessary to run post install patcher and uncheck the one that you want to deactivate?

You must reinstall. Wipe the drive if you can. Unchecking does not remove the patches.

 

[TimothyR734]

Yeah, I just saw it was only for that disk but then I read you titled it macOS Mojave. What make/model for your HDD? My internal Hitachi HTS545025B9SA02 Media has Mojave running on it just fine. Was it an HFS+ drive or APFS? There has been issues with APFS installing on HDDs.

APFS runs fine on HDD but only if you use the APFS Rom Patcher successfully. The only disadvantage of HFS is that you will not be able to use the software update in order to use the software update your hdd/ssd has to be APFS to get the next beta or create a new Mojave patcher download the new beta create a bootable patcher and either install clean or install over the previous beta

 

[thegurgz]

APFS runs fine on HDD but only if you use the APFS Rom Patcher successfully. The only disadvantage of HFS is that you will not be able to use the software update in order to use the software update your hdd/ssd has to be APFS to get the next beta or create a new Mojave patcher download the new beta create a bootable patcher and either install clean or install over the previous beta

Do you think I don't know that? I've been following this thread for 75 pages, and have been an active member, just like you. I, along with others, have had issues recently with APFS on HDDs, so I was just informing them that that could be the problem. I was the one that showed proof that HFS+ was the cause of not being able to update natively and you need to convert to APFS! I know you are trying to help, but there isn't a need to tell regulars what they have read many times in recent pages.