macOS 10.14 Mojave on Unsupported Macs Thread

[@ioith]

maybe try running this, I use this when I install kexts but it also repairs permissions see if that changes anything

Fixing permissions still does not let me login to the icloud or appstore

 

[TimothyR734]

Fixing permissions still does not let me login to the icloud or appstore

https://www.icloud.com have you tried signing in and out here. check the settings

 

[@ioith]

https://www.icloud.com have you tried signing in and out here. check the settings

I have successfully logged in online on the same mac ,

When i attempt to sign in multiple times on the appstore i get returned that my password was entered incorrectly even though it was correct.
Do i need to disable sip to run kext utility?as i was getting that kext utility was not able copy kext from source file.

 

[TimothyR734]

I have successfully logged in online on the same mac ,

When i attempt to sign in multiple times on the appstore i get returned that my password was entered incorrectly even though it was correct.
Do i need to disable sip to run kext utility?as i was getting that kext utility was not able copy kext from source file.

Are you trying to install a kext yes if you are on a unsupported Mac it is necessary to leave SIP disabled

 

[@ioith]

Are you trying to install a kext yes if you are on a unsupported Mac it is necessary to leave SIP disabled

Tried it still doesnot work

 

[Sylverton76]

maybe try running this, I use this when I install kexts but it also repairs permissions see if that changes anything

Thanks for the attachment. Unfortunately the Mojave patcher for the MB4,1 changes global permissions rather than just the kext folders (i.e. /S/L/E and /L/E). I believe Kext Utility sets the permissions and ownership on the /S/L/E folder and then rebuilds the cache. Disk Utility used to be able to reset global permissions but this function disappeared with El Capitan. System Integrity Protection would usually protect users from being able to change global permissions but of course SIP is disabled on unsupported Macs.

 

[TimothyR734]

New macOS Mojave Dev beta available successfully installed but a bit more buggy got down to 2 mins of installation no process of the progress then went to 1 minute then rebooted so might be firmware updates with this one New+ taking forever to load FaceTime and iSight are working. iTunes , stocks, voice memo's work but beachballs while loading. Hybrid patches are working this one is the most memory hogging beta I have 4GB ram and with this beta I can barely keep 600 MB free something is eating it and much slower than 10.14.4 I think its worse

 

[TimothyR734]

Figured out why my MacBook 5,2 was slow my HDD which I bought brand new still unopened 320 gb HDD became corrupted and I haven't had a week yet

 

[Kevbasscat]

Are you trying to install a kext yes if you are on a unsupported Mac it is necessary to leave SIP disabled

If you watch the !0.15 Catalina bug reports, for the past week signing into accts. across the board has been hell for even supported devices. iCloud, iTunes, Appleid, you name it. You might try looking at their fixes. Just an idea. Even for Mojave also.

 

[@ioith]

New macOS Mojave Dev beta available successfully installed but a bit more buggy got down to 2 mins of installation no process of the progress then went to 1 minute then rebooted so might be firmware updates with this one New+ taking forever to load FaceTime and iSight are working. iTunes , stocks, voice memo's work but beachballs while loading. Hybrid patches are working this one is the most memory hogging beta I have 4GB ram and with this beta I can barely keep 600 MB free something is eating it and much slower than 10.14.4 I think its worse

Using dosdudes tool or julians?

 

[TimothyR734]

Using dosdudes tool or julians?

Dosdudes it seems to be smoothing out some today less beachballs I ended up doing a clean install

 

[@ioith]

Thanks for the attachment. Unfortunately the Mojave patcher for the MB4,1 changes global permissions rather than just the kext folders (i.e. /S/L/E and /L/E). I believe Kext Utility sets the permissions and ownership on the /S/L/E folder and then rebuilds the cache. Disk Utility used to be able to reset global permissions but this function disappeared with El Capitan. System Integrity Protection would usually protect users from being able to change global permissions but of course SIP is disabled on unsupported Macs.

I dug into wheel , it turns out that that su(0) is the root user and wheel is su(1) user hence the earlier when we got the uid 0 error while using sudo , it was indeed as u said due to an error in permissions but i could not find anything on global permissions

 

[NazgulRR]

Nope, Mojave Patcher will not automatically convert drives to APFS in any circumstance.

Cheers! Sounds like a safe procedure in that case as I'd prefer not to risk bricking the machine with the ROM. Hope 10.4.6 lands soon. I'll report back.

Have just gone ahead with the in place upgrade from 10.11.6 > 10.14.5. Smooth process, kept the DIY Fusion drive on HFS+ too.

Thanks so much for the tool and support!

 

[protocold]

sorry I get all confused with reading and following the thread.

I have a macbook 5,2. is the APFS rom patcher working for this or should I stick with post install patch instead?

When I try to run APFS rom patcher, it let me picks:
MX25L3205(A)
MX25L3205D/MX25L3208D
MX25L3206E (default selected)

But all these 3 different chips are 4MB SPI. Why would they make any difference?

 

[dosdude1]

sorry I get all confused with reading and following the thread.

I have a macbook 5,2. is the APFS rom patcher working for this or should I stick with post install patch instead?

When I try to run APFS rom patcher, it let me picks:
MX25L3205(A)
MX25L3205D/MX25L3208D
MX25L3206E (default selected)

But all these 3 different chips are 4MB SPI. Why would they make any difference?

Based on my experience, the MX25L3205D/MX25L3208D chips are what most MB5,2 machines use. Just be VERY careful, though, as if that machine enters sleep mode or powers off during the flashing process (which can take longer than 30 minutes in some cases), it WILL brick the system.

 

[slimmy18222]

I have both brightness control and sleep working in Mojave on my 15" mbp with a broken gpu that won't even boot unless disabled, this is how I did it :

(If you want to try this method, just apply the post install patches again and start from #3.)

1 boot into single user mode and set nvram variable:

sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

2 install Mojave, then apply patches.

3 boot into single user mode again, type:

/sbin/mount -uw /

mkdir AMD

mv /System/library/Extensions/AMDRadeonX3000.kext AMD/

reboot

4 open terminal, type:

sudo mkdir -p /Library/LoginHook

sudo nano /Library/LoginHook/LX3000.sh

contents:

#!/bin/bash
kextload /AMD/AMDRadeonX3000.kext
exit 0

press ctrl + x to exit and y to save.

sudo chmod a+x /Library/LoginHook/LX3000.sh

sudo defaults write com.apple.loginwindow LoginHook /Library/LoginHook/LX3000.sh

5 set gpu for sleep to integrated:

sudo pmset -a gpuswitch 0

reboot

6 check that x3000 is loaded and gpu is set to integrated

sudo kextstat | grep AMD

pmset -g

compare to the screenshot to make sure its correct.

7 optional, increase vram for hd3000 using Jacklukes method here

You have to do #1 again each time the nvram is reset.

Oh my fault, didn't know sorry.

@arqueox try these steps they 100% work this time to increase from stock 512 MB to 1536 MB VRAM:

cd /S*/L*/Ext*/AppleIntelSNBGraphicsFB.kext/C*/M*

sudo cp AppleIntelSNBGraphicsFB AppleIntelSNBGraphicsFB.backup

sudo perl -pi -e 's|\xC7\x45\xD0\x00\x00\x00\x20|\xC7\x45\xD0\x00\x00\x00\x60|g' AppleIntelSNBGraphicsFB

sudo touch /S*/L*/Extensions


edit:
thanks to @arqueox for having tested the Info.plist
before reboot/restart you have to edit this file:

/System/Library/Extensions/AppleIntelHD3000Graphics.kext/Contents/Info.plist

Adding after these strings, this part:

<key>VRAMMethod</key>
<integer>0</integer>
<key>VRAMOverride</key>
<integer>0</integer>
<key>VRAMSize</key>
<integer>1536</integer>

after edited the plist from Terminal type:

sudo chown -R 0:0 /System/Library/Extensions && sudo chmod -R 755 /System/Library/Extensions

sudo kextcache -i /

sudo reboot

Hello, I have both brightness control and sleep working in Mojave on my 17" mbp with a broken gpu using your method, but i cannot increase vram for hd3000 using Jacklukes method because after that won't load mac os unless i re-apply NVRAM variable (but no vram increase anyway)

@Olivia88 @jackluke

 

[protocold]

Based on my experience, the MX25L3205D/MX25L3208D chips are what most MB5,2 machines use. Just be VERY careful, though, as if that machine enters sleep mode or powers off during the flashing process (which can take longer than 30 minutes in some cases), it WILL brick the system.

Many thanks for your quick reply!

So i need to make sure the machine doesnt sleep and ensure the power supply is solid before I start?

I have an external SPI programmer and the hotgun/tools to desolder this if necessary in case it messed up. Just that I dont want to open the macbook unnecessarily!

 

[avz]

Successfully updated my MacBook5,1 to .6 Public Beta 4. For some reason the update came up as .6 Public Beta 3 in System Preferences/Software Update, but after the update it displayed as Developer Beta 4 in the Installations.

 

[jackluke]

Hello, I have both brightness control and sleep working in Mojave on my 17" mbp with a broken gpu using your method, but i cannot increase vram for hd3000 using Jacklukes method because after that won't load mac os unless i re-apply NVRAM variable (but no vram increase anyway)

@Olivia88 @jackluke

For VRAM increase try these: IntelHD3000 pre-patched VRAM HighSierra/Mojave

 

[Vyzantion]

Could some please check the Gatekeeper, XProtect and MRT versions on System Information? A MRT update was issued last night and I want to make sure there was not another security update that might have failed to install (It has happened in the past on Mojave.).

 

[avz]

Could some please check the Gatekeeper, XProtect and MRT versions on System Information? A MRT update was issued last night and I want to make sure there was not another security update that might have failed to install (It has happened in the past on Mojave.).

All the latest security updates happened to be visible in my post above. There are no others.

 

[Vyzantion]

All the latest security updates happened to be visible in my post above. There are no others.

XProtect and TCC are not visible. What about them? I wonder if only MRT shall be updated and not the rest, it does not make sense to me.

 

[avz]

XProtect and TCC are not visible. What about them? I wonder if only MRT shall be updated and not the rest, it does not make sense to me.

XProtect and TCC are not visible because Apple did not update them recently. So 2103 and 17.0 accordingly.

 

[Yiorlis59]

Dosdudes it seems to be smoothing out some today less beachballs I ended up doing a clean install

Is the beta working okay now?

 

[Kevbasscat]

Based on my experience, the MX25L3205D/MX25L3208D chips are what most MB5,2 machines use. Just be VERY careful, though, as if that machine enters sleep mode or powers off during the flashing process (which can take longer than 30 minutes in some cases), it WILL brick the system.

Plug it in and disable sleep mode before attempting.