Thanks!
Thanks!
I think I would try a different hdd/ssd it could be going badFound 20 orphan dstream id objects from a snapshot… I’m new to APFS so I have no idea what this means.
I don't know what machine you are on, or your history with installing betas, but I would consider doing a fresh APFS install on your device. You obviously have a current patcher stick - so save your data if you have to and reformat your main boot disk as APFS. Installing over betas can introduce some unexpected results (also makes it harder for us to help)Another day, another issue. Downloaded the update from system preferences, it rebooted and ran full install. Booted into prohibitory, booted onto patched usb stick. Ran them, forced cashe rebuild. Now my recovery disk for Mojave is gone from startup options, and refuses to boot into Mojave. Will run mostly through, then reboot so most likely good ol kp. I just don’t understand what happened this time.
Thanks for the encouragement. Just installed a clean copy of DP7, using macOS Mojave Patcher 1.1.2, after reformatting the HDD partition to APFS. Everything went like clockwork. So far, no weird processes hogging my CPU and all things seem normal.Could have just been an error from the early betas, or a patcher error since back in DP3 the creators were still figuring out graphics acceleration and such, so the patcher wasn’t completed. It should work like a charm especially since APFS is natively supported, but if it doesn’t, save the installer log and I’m sure this forum will help you out and get it all running!
when I do it will be when I get a ssd and I am looking for a 4 gb dd2 ram so I can go from 4 GB to 6gb of ramNo problem. If you do decide to check the board. Don't forget to check both sides!
Mojave runs perfectly well on APFS but it would be wise to use you macOS Mojave patcher to format your drive and do a clean install of Mojave betaI have high sierra on a APFS drive, (iMac 27 late 2011), when trying to format the usb stick the only option I get is APFS, if I manage to format it on a different machine, and run the patcher on my iMac will Mojave install without destroying my APFS formatted drive?
I don't know what machine you are on, or your history with installing betas, but I would consider doing a fresh APFS install on your device. You obviously have a current patcher stick - so save your data if you have to and reformat your main boot disk as APFS. Installing over betas can introduce some unexpected results (also makes it harder for us to help)
Good luck.
Just got the 2.8, 1TB off refurb in April luckily. HS still sucks though. Feels like a 10 year old machine.Or just sell your actual Macbook as long the most people don't know yet its unsupported and buy yourself a good spected Retina Macbook from 2014-15. The new ones seem to have a lot of Problems so you might be better off with them for less money.
A disposable like the phones, except the phones last longer.force people to buy a dongle computer.
Alright, I've finally finished it... APFS ROM Patcher is finally done! Some precautions:
- APFS ROM Patcher is to be used AT YOUR OWN RISK! There is always the possibility that your machine could become bricked as a result.
- DO NOT apply APFS ROM Patcher if your machine already can boot from APFS volumes
- If you get the following dialog, it is HIGHLY RECOMMENDED that you open your machine, remove your logic board if necessary, and verify the exact EEPROM type your machine has. Selecting the wrong EEPROM model will MOST LIKELY result in a bricked system!
View attachment 776034
Download here. Please be sure to post results!
[doublepost=1534421648][/doublepost]I know, I temporarily removed it until I figure out the random code signing issues, which will cause the machine to fail to boot.
did you try the legacy audio patch in patch updater and is your hdd/ssd hfs or apfsMy mac pro-2008 is now not detecting any audio devices what so ever.
[doublepost=1534426770][/doublepost]Software Updater is unable to find DP7. I am still on DP6. Is this normal?
They are traditionally very similar. I've never actually compared a public beta from a developer preview. At the very least the difference would be how they were built: a dp would have more instrumented code and debugging support than a public beta so that bug and crash reports become more meaningful to Apple engineering. Especially if it's a critical bug or crash they have to work with you on.Public beta 6 is virtually identitcal with Developer Preview 7? I remember I have updated to PB6, but checking the installation history, it says DP7. Usually the PB that comes a day later from a DP would have the same version?
Did you install the kext correctly using kext utility or kext wizard?
Is SIP set to off? If not, boot from USB Mojave patcher installer, launch Terminal and do: sudo csrutil disable
Then try again.
onyx not yet available for mojave.maybe try onyx
Hfs and Hdd it says installed version is 0did you try the legacy audio patch in patch updater and is your hdd/ssd hfs or apfs
did you try and reset your password or not entered the password correctlyHi, I've got another issue.
After updating mojave to DP7 I wanted to install Night Shift again.
It always worked for me. But this time the system didn't boot anymore. So I reinstalled mojave via the patcher, or I tried.
I got an error that it couldn't be installed on the volume so I checked it with disc utility and apparently there was an issue with my start volume that couldn't be fixed.
So I wiped the disc, did a fresh install and migrated my system.
My keychain got broken or forgot all my mail passwords and and after fixing this I can't log in to icloud any more.
View attachment 776340
[doublepost=1534448483][/doublepost]Though I'm still logged in at the App Store..
your hdd has to be formatted APFS to get the update from software update version 0 is correct as there has been no update to the legacy audio patch try clicking on about this Mac then system report-audio-devices see f anything is listed then check to see if the volume is turned downHfs and Hdd it says installed version is 0
did you try and reset your password or not entered the password correctly