Can you share the steps you took to complete your setup and where you downloaded that beta from? I have that same exact machine but every time i patch it and make an installer I cant seem to boot to my computer
Thanks
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Thanks
@webg3 meant "no app crashing" not "no KP", you know I have same your Macbook7,1 and also there I have News.app working (but w/o News+).
It's odd, tried to change language region but still no News+, we can exclude the GPU type, since News+ crashes both on Nvidia Tesla and IntelHD3000, and at this point I'd exclude also the way of patching kexts, I read that also someone located in Europe has News+ "pane" and consequently News.app crashing during scrolling, but the only clue we had is simply to those who OTA updated and got "News+" disappeared, then News.app doesn't crash.
I meant all this in accelerated non-metal environment, because "kext-unloading" the GLDriver News+ doesn't crash more to anyone.
About the future of these "iOS apps", surely we'll know more on .5 final release, and much more on .15 beta , they're both not so far.
[doublepost=1556786251][/doublepost]
Last edited:
Sorry, I did not specify, have no problem, no Kernel Panic or crash in News.
News+ is not available for me, nor does it appear button.
I can search normally and scroll the page, News works like a charm.
Well, if Apple changes more core apps like News this summer will be interesting to say the least... just for kicks I tried swapping out the entire set of News frameworks in iOSSupport priv franeworks to “resurrect” a .3 version of News but no go. Obviously more complex than that.
Took pkouame's advice and installed .4 onto a APFS HDD from the USB "stick" made w/ patcher 1.3.1. Then enrolled the iMac into MacOS Beta Program here: https://beta.apple.com/sp/betaprogram/welcome
Once enrolled .5b4 appeared on Software update CP after about 10 minutes. Installed from CP, then re-patched after booting into USB "stick". Reboot the iMac11,2 APFS HDD into .5b4. Success. So far, everything seems to work except News+.
APFS HDD performance is acceptable, SSD is advised but difficult on iMac11,2.
Make certain the NVRAM is reset, TWICE or boot drive selection cannot be made. Option key at restart.
Last edited:
The MacBooks 13" will work anyway without KPs, while if you meant the 15" or 17" aka the dualGPUs, then .5 beta 4 will work enough fine, much better than 10.14.4 and roughly on par with 10.14.3, after you applied the known dosdude1's patches, to raise zero the KP you could try this additional archive , moreover it will add the correct GPU switching from gfxcardstatus.app .
But if try that archive you have to know enough well how to operate from single user mode, chown/chmod and so on to properly install the kexts and frameworks contained.
Last edited:
I created a patched Mojave USB installer (Mojave 10.14.4, patcher 1.3.0) to upgrade my HackBookPro 7,1 (T9300 CPU, NVidia Quadro NVS 140m, Atheros AR5416 Wi-Fi) from High Sierra 10.13.6 to Mojave 10.14.4. High Sierra 10.13.6 runs perfectly on this laptop.
When I attempt to boot from the patched Mojave USB installer, the installer boot sequence is stuck in a repeating loop of
I have tried setting the Mac Model in the CLOVER config.plist to both MacBookPro 4,1 and MacBookPro 7,1 but the boot behavior is the same in both cases.
Does anyone have any idea why the USB installer boot sequence might be stuck in this loop?
When I attempt to boot from the patched Mojave USB installer, the installer boot sequence is stuck in a repeating loop of
localhost com.apple.xpc.launchd[1] (com.apple.trustd.801) <Warning>: Service exited with abnormal code: 1
localhost com.apple.xpc.launchd[1] (com.apple.trustd) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
localhost com.apple.xpc.launchd[1] (com.apple.locationd.802) <Notice>: Service exited due to SIGSEGV | sent by exc handler[808]
localhost com.apple.xpc.launchd[1] (com.apple.locationd) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 3 seconds.
localhost com.apple.xpc.launchd[1] (com.apple.WindowServer.803) <Warninge>: Service exited with abnormal code: 1
localhost com.apple.xpc.launchd[1] (com.apple.WindowServer) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
localhost com.apple.xpc.launchd[1] (com.apple.pluginkit.pkd.805) <Notice>: Service exited due to SIGABRT
localhost com.apple.xpc.launchd[1] (com.apple.pluginkit.pkd) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
localhost com.apple.xpc.launchd[1] (com.apple.trustd) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
localhost com.apple.xpc.launchd[1] (com.apple.locationd.802) <Notice>: Service exited due to SIGSEGV | sent by exc handler[808]
localhost com.apple.xpc.launchd[1] (com.apple.locationd) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 3 seconds.
localhost com.apple.xpc.launchd[1] (com.apple.WindowServer.803) <Warninge>: Service exited with abnormal code: 1
localhost com.apple.xpc.launchd[1] (com.apple.WindowServer) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
localhost com.apple.xpc.launchd[1] (com.apple.pluginkit.pkd.805) <Notice>: Service exited due to SIGABRT
localhost com.apple.xpc.launchd[1] (com.apple.pluginkit.pkd) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
I have tried setting the Mac Model in the CLOVER config.plist to both MacBookPro 4,1 and MacBookPro 7,1 but the boot behavior is the same in both cases.
Does anyone have any idea why the USB installer boot sequence might be stuck in this loop?
Attachments
Last edited:
Since this is a Hackintosh, there could be several issues unrelated to our efforts and you might have more success posting somewhere like insanelymac. However, we can definitely look into it and see if our knowledge overlaps. The main problem here looks like the WindowServer crash. I'm not sure why that happens, though, since the installer BaseSystem typically runs without acceleration anyways.
There is all kinds of weirdness that can happen in the BaseSystem/recovery environments and it's tricky to troubleshoot. You might try a manual install of the package to a separate partition using Installer.app in High Sierra (I can walk you through this if necessary). Then we can debug a lot more effectively in the full system. Since your GPU is similar to the GeForce 8600, you'll probably eventually need to use our nVidia Tesla legacy graphics patch, but we'll deal with that once we get you booting without acceleration.
Security update issue this morning. It appears some security updates were installing in the background this morning, when I clicked on reboot. It worked really hard for Mojave to boot into my Hackintosh. I have checked the System Information app on installations and it appears that one of the security features of macOS, XProtect, was updated. But MRT, another one that was suppose to be updated alongside XProtect was not. I have checked for updates and the update was not visible.
According to this
https://eclecticlight.co/2019/05/02/apple-has-pushed-updates-to-both-xprotect-and-mrt/
XProtect was suppose to be on version 2103 and installed on 2.05.2019 , and MRT of 1.41 and updated on the same day. It says on MRT that is 1.41 but no update for it today and the version of the app is dated on 27.04.2019 . Could someone please check on the System Information app this:
1. On Software/Installations if there are any updates for both XProtect and MRT dated for 2.05.2019
2. On Software/Applications the version and the date of the MRT app.
If what it says does not fit what I have, it means that, probably, a failed installation corrupted the MRT and I need to reinstall the OS. I know the dosdude1 way of installing disables integrity checks into the OS and that can cause issues on certain situations.
According to this
https://eclecticlight.co/2019/05/02/apple-has-pushed-updates-to-both-xprotect-and-mrt/
XProtect was suppose to be on version 2103 and installed on 2.05.2019 , and MRT of 1.41 and updated on the same day. It says on MRT that is 1.41 but no update for it today and the version of the app is dated on 27.04.2019 . Could someone please check on the System Information app this:
1. On Software/Installations if there are any updates for both XProtect and MRT dated for 2.05.2019
2. On Software/Applications the version and the date of the MRT app.
If what it says does not fit what I have, it means that, probably, a failed installation corrupted the MRT and I need to reinstall the OS. I know the dosdude1 way of installing disables integrity checks into the OS and that can cause issues on certain situations.
Last edited:
Thank you for your quick reply! I don't want to waste your time chasing something unique to my system. I have successfully used the patched Mojave installer (version 1.3.0) to upgrade my HackPro 5,1 (NVidia GeForce 9800GT) to Mojave 10.14.4, so I had hoped to have the same success with my HackBookPro 7,1. I'll try a few ideas of my own and report back if I succeed or have more questions. Thank you.
What about the receipts on System Information app, on Software/Installations ? What is listed there on XProtect and MRT and what are the dates of installation? MRT might have got the update earlier, but on some systems it might get installed on the same day as XProtect, if the OS was busy and had not time to update.
What machine is it? You may also need to re-install the Volume Control Patch.
OK, although I have left and gone back to 10.12.6 on my MBP 7,1, AND thank you everyone for the ability to play, especially DosDude1 for all his efforts and genius patchers and whatnot!!! I had a bit of problem reverting that DD1 so graciously helped with. But when that kinda didn't work and I had to do some other things to get it to work, one thing was off, which is where I have one question.
"On reboot I got a single tone, then the start up chime and when the startup screen come up, but the progress thermometer was wide, outlined with rounded ends. After a "normal" startup after that, everything seems OK. I searched and searched and found every beep, bulp and blip and startup codes ever, except that one."
Does anyone know what that tone and start up page means or what caused it? I'm OK now, but would like to know what happened . . .
Any assistance will be greatly appreciated.
Thank you . . .
. . . fb
So long and may be see you all in the future. TTFN!
"On reboot I got a single tone, then the start up chime and when the startup screen come up, but the progress thermometer was wide, outlined with rounded ends. After a "normal" startup after that, everything seems OK. I searched and searched and found every beep, bulp and blip and startup codes ever, except that one."
Does anyone know what that tone and start up page means or what caused it? I'm OK now, but would like to know what happened . . .
Any assistance will be greatly appreciated.
Thank you . . .
. . . fb
So long and may be see you all in the future. TTFN!
Last edited:
It did a firmware update, so nothing to worry about.
"Thank You!" It's been so long that I have had that done, I totally forgot about it. Totally surprised it didn't show up in any of the searches I did.
Bye Guys.
I have a fully functioning Mac Pro 4,1 running mojave 100% with no crashes or graphics issues.
System specs:
Mac Pro 4,1 8 gigs of ram 1TB Hard drive
HD Radeon 4870 512 megs of ram.
using apfs patcher no problems
store not crashing full graphics acceleration
[doublepost=1556855148][/doublepost]can also confirm upgrading Mac Pro from firmware 4,1 to 5,1 helps boot apfs faster
System specs:
Mac Pro 4,1 8 gigs of ram 1TB Hard drive
HD Radeon 4870 512 megs of ram.
using apfs patcher no problems
store not crashing full graphics acceleration
[doublepost=1556855148][/doublepost]can also confirm upgrading Mac Pro from firmware 4,1 to 5,1 helps boot apfs faster
iMac 9,1. But there is no Volume Control Patch on the Patch Updater, even in the Post-Installer Patcher. Where is this Volume Control Patch?
Last edited:
Apparently, you are up-to-date.
If granularity is necessary, try SystHist 1.8 from the same developer.
Last edited:
@ASentientBot, After further testing, I have reason to believe that the problem happens only when booting the patched installer from USB. If you don't mind telling me how to "try a manual install of the package to a separate partition using Installer.app in High Sierra," that would be great. Thank you.
What do you mean by granularity, in this context?
The app did not provide any new information then I already had from System Information, regarding the issue. No, I think MRT is broken, since the app is dated as modified into 27 of april, not 2 of may and no receipt for the update. System Information, on Software/Installations lacks a receipt for MRT, but has one for XProtect. Previous updates of MRT had a receipt. I hate this Apple policy to keep thoose updates hidden, I would much have prefered to see them coming into System Preferences, alongside other updates. The installation of these updates easily get corrupted, I have had some nasty experiences in the past on them.
By the way, on your machine TCC is version 15, instead of 16, like on mine. This suggests that you have at least one corruption issue yourself. I admit, I am pretty paranoid regarding security features and security updates, but like can be really tough today on cyber security, as you surely know.
The dosdude1 method has some vulnerabilities. Last mounth Gatekeeper has had an update from the beta cycle, then the current update. On the Insanelymac forums I was told this was not suppose to hapend, that the macOS installation has some issues, potentialy serious. I have reinstalled the OS after that and Gatekeeper updated fine.
Last edited: