I have an issue - I managed to upgrade El Cap --> Mojave, directly, by temporarily telling clover to use Fake CPU ID 0x0106E0 (manually re-entering that upon successive reboots, during installation), but AFTER installation, I still have to use that CPU ID, or it won't boot.
I'm on a G3258 Pentium, currently on High Sierra with no issues. However, each time I edit config.plist and put the fake cpu id in and try to boot Mojave installer, I either get it hung at "Randomseed" blah blah, or it just spits out the dummy and reboots
Yes, that's correct.
Additionally, I disconnected my ethernet from the machine, and connected to a mobile hotspot, to eliminate the router being the cause of the issue; the issue remains.
If I send myself an image on my iPod, it shows sent/received on iPod AND Mac… and if I...
High Sierra is working flawlessly on my Asus Z97-P + G3258... except "Messages" sends everything *except* images. I can receive images, but not send them. I've logged out/in of my iCloud account, rebooted a few times, but to no avail.
Would someone be able to help me, please?
Thank you, have a...
Thank you! :D
I've had El Cap on my Asus Z97-P for almost 2 years. I run it with 8GB RAM, a Samsung EV0 850 250GB, and an MSI Nvidia GT210 (yes, I know it's pretty weak, plan on getting a better one for iMovie.)
I followed the guide, put "NullCPUPowerManagement.kext" in the "Other" folder...
I got Sierra installer working - I hadn't put the Intel null power thingamajig kernel extension in the folder named "other" on the USB installer. Having done that, and copying my el cap config.plist over to the installer, it booted fine and installed on my spare test hdd.
~ Mobo: Asus Z97-P
~ GPU: MSI 1GB Nvidia GT210 (PCI-E card)
~ CPU: G3258 (I use fakecpuid=0x0306A0 with El Cap, no issues at all)
~ RAM: 4x2GB DDR3
~ I used "Nvidia injection" when creating the Sierra USB installer, as I have a GT210, works in El Cap, as everything else does.
I take it that because I, previously, hadn't known about, ergo hadn't enabled "without caches", that was what prevented the upgrade install boot option from booting the Sierra installer (launched as an upgrade within El Cap, I might add - I am not talking about a USB-based installer) further...