Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Hi

Any one got any issues updating with FileVault enabled.. when trying to install, it shows the drive doesn't have enough space, if I go to the disk utility I can't get to the mount the APFS volume.

if I click on the file menu from the disk utility, it gets stuck with the beach ball.

I managed to disable the FileVault and install.. but was getting errors.

Attaching the error log.

Regardless, I ran the patches, it booted fine with Public beta 3.
 

Attachments

  • Installer Log 19-Jul-2018.txt
    445.1 KB · Views: 438
Last edited:
  • Like
Reactions: TimothyR734
Huge thanks to all of you for your work on this patch! My MacBook Pro 2010 works great with Mojave (except for the iSight but I'm working on it...)
Is it just me or since the latest beta (Public beta 3 /dev beta 4) dynamic wallpaper works.
It is awsome to see it change during the day!

Use kext from High Sierra 10.13.6 (all five IOUSB)
[doublepost=1532020961][/doublepost]
Hi, first let me congratulate the OPs of this forum for taking the time to make this work.
I was able to install dev beta 3(18A326h) in my Imac 10,1 and everything is working fine except the isight camera. But that's not a problem. The problem now is that I would like to update instead of a fresh install, but system update always tell me that my Mac is up to date. I already patched. several times, the system update patch from patcher updater but nothing. Is there another way to update to beta 4? Thanks!
Yes, install "macOS Plubic Beta Access Utility"
 

Attachments

  • Captura de Tela 2018-07-19 às 14.16.57.png
    Captura de Tela 2018-07-19 às 14.16.57.png
    1 MB · Views: 187
  • Like
Reactions: TimothyR734
Use kext from High Sierra 10.13.6 (all five IOUSB)
[doublepost=1532020961][/doublepost]
Yes, install "macOS Plubic Beta Access Utility"

@DaVroX
If you upgraded to dev beta4 from the system, please share your experience swapping those 5 kexts from @webg3.

I got iSight to work consistently on beta3 for a while. Since I upgraded to dev b4, iSight has been spotty at best. Seems like I have to catch FaceTime or PhotoBooth at the right time before it decides to stream video.

On the plus side, when iSight does work the video stream is MUCH improved: much less noise - a softer image - effects working. So there is hope...

By the way I'm on an mbp 5,3 mid 2009.
 
  • Like
Reactions: TimothyR734
Dear dodsude & team :)

As first, and always, let me thank for your tireless and fantastic work ! Compliments !


Regarding to main informations from first page, MacMini 3.1 has already a "usable" status, with graphics acceleration, except UI glitches (my WiFi card is changed since High Sierra update).

I leave the upper mentioned machine in life for daily - hours long office work, its tuned to max possible, and its still a nice usable computer.
Because the graphics is weakest part of the machine, i used High Sierra only WITHOUT any effects (including transparency OFF, etc...).

Can you / anybody tell me please about the UI glitches without transparency ? Is the interface fully glitch free in light/dark with effects OFF, or are they just "reduced" ? How significant are this glitches ?

Thank you !
 
Dear dodsude & team :)

As first, and always, let me thank for your tireless and fantastic work ! Compliments !


Regarding to main informations from first page, MacMini 3.1 has already a "usable" status, with graphics acceleration, except UI glitches (my WiFi card is changed since High Sierra update).

I leave the upper mentioned machine in life for daily - hours long office work, its tuned to max possible, and its still a nice usable computer.
Because the graphics is weakest part of the machine, i used High Sierra only WITHOUT any effects (including transparency OFF, etc...).

Can you / anybody tell me please about the UI glitches without transparency ? Is the interface fully glitch free in light/dark with effects OFF, or are they just "reduced" ? How significant are this glitches ?

Thank you !
The glitches are nonexistent when using "Reduce Transparency" or I believe high contrast mode.
 
Dear dodsude & team :)

As first, and always, let me thank for your tireless and fantastic work ! Compliments !


Regarding to main informations from first page, MacMini 3.1 has already a "usable" status, with graphics acceleration, except UI glitches (my WiFi card is changed since High Sierra update).

I leave the upper mentioned machine in life for daily - hours long office work, its tuned to max possible, and its still a nice usable computer.
Because the graphics is weakest part of the machine, i used High Sierra only WITHOUT any effects (including transparency OFF, etc...).

Can you / anybody tell me please about the UI glitches without transparency ? Is the interface fully glitch free in light/dark with effects OFF, or are they just "reduced" ? How significant are this glitches ?

Thank you !

As far as I can tell all transparency-related user interface glitches that are caused by having a pre-metal graphics card are gone after enabling Reduce Transparency. With that being said, there are still other user interface glitches present caused not by the unsupported hardware but by Mojave itself. The pre-metal graphics card glitches are quite severe as they affect all transparent areas of the system when in light mode.
[doublepost=1532023049][/doublepost]
The glitches are nonexistent when using "Reduce Transparency" or I believe high contrast mode.

Do you believe that there is an actual albeit unfound solution to these glitches or has it been declared unsolvable and only fixable by using a workaround?
[doublepost=1532023119][/doublepost]
The glitches are nonexistent when using "Reduce Transparency" or I believe high contrast mode.

Increase Contrast actually enables Reduce Transparency as well so the two workarounds are one in the same.
 
Dosdude - thank you very much for fast reply ! Very usefull informations !

Julian - also thanks very much for help ! So, the main solution is to set transparency off, as i done up to now, great !
As you mentioned, there are still glitches present. Are this glitches/ errors restricting the user in work / making work impossible, or are they just "cosmetics" which are sometimes in some situations present ?

Thank you !
 
  • Like
Reactions: TimothyR734
@DaVroX
If you upgraded to dev beta4 from the system, please share your experience swapping those 5 kexts from @webg3.

I got iSight to work consistently on beta3 for a while. Since I upgraded to dev b4, iSight has been spotty at best. Seems like I have to catch FaceTime or PhotoBooth at the right time before it decides to stream video.

On the plus side, when iSight does work the video stream is MUCH improved: much less noise - a softer image - effects working. So there is hope...

By the way I'm on an mbp 5,3 mid 2009.


Sharing an installation experience.

Successful installation of Mojave, up to developer beta4, with full iSight camera functionality, on
Macbook Pro 5,2 - mid 2009, Core2duo 3.06 MHz, 8 MB of RAM, hybrid Seagate HD (with APFS format)


I installed Mojave beta with first reiteration of dosdude1’s Mojave patcher, using a 16 GB USB stick, and steps identical to installing High Sierra. Mojave was installed on top of High Sierra 10.13.6 (beta version at the time).

First reboot, after installation, caused laptop to continually reboot. I pressed option key, after second loop, and this “brought up” the screen listing the drives/volumes available. I chose the USB stick, and booted back into the patcher, launched “post install patcher,” selected my computer model from dropdown menu, and re-patched the drive.

Reboot proceed smoothly, until a document appeared on the screen, and a dialog box with a warning, that “installation could not complete…” and “offering” a selection of action choices, including “restart.”

I restated with option key pressed, and chose once more to boot into the USB drive, and launched post-install patcher. This time I checked “force cash rebuild” function, and then “reboot.”

The installation went without a hitch, and I was greeted with login screen.

The system was slow for a length of time; activity monitor showed many processes that are invoked by new system installation, ie, system optimization, indexing, etc.

All system functions were available, except the iSight camera, and few other minor glitches (already reported by others), including lack of “dynamic desktop” function. I did have full graphic acceleration on both Nvidia 9600M GT and the 9400M cards. System was visibly more responsive than HS.

Subsequent developer betas were installed using Apple’s download utility. Installing this utility launches the software update utility, located in system preference panel, which then links to actual download file.

Latest developer beta (18A336e) did require patching, due to recurring booting loop. Pressing option key to interrupt the “looping”, then booting back into the USB stick, activating post install patcher, and re-patching, fixed the issue and update fully installed.

The latest developer Beta–4 fixed “dynamic desktop” function, but the iSight camera still did not work.

Using guidelines from posters here, I extracted from High Sierra 10.13.5 installer the IOUSBHostFamily.kext and IOUSBFamily.kext, and “placed” them on Mojave desktop. Then, I downloaded an application “KextBeast,” and followed instruction within it, to install the two kexts into Mojave’s system/Library/extensions folder.

*Warning,* as noted by other posters here, just moving the kexts into the Mojave’s system extensions folder will not work, unless set of specific terminal commands are executed afterward. KextBeast app. is just one of several applications, which can properly install those Kext items. If a restart is attempted without the above Kext processing, computer will boot into the login screen, but the cursor will be “frozen,” because all USB devices (including external ports) will be disabled.

Following replacement of Kexts, a restart resulted in boot-looping. So, again, I used option key to boot back into the USB stick, launched the patcher, re-patched, rebooted, and was greeted by login screen.

Once logged in, I found the iSight camera worked perfectly, without any apparent collateral damage.

Currently the System is very fast, and stable. The CPU idles at > 97% ( up to 98%), when no applications are engaged, other than Activity Monitor.

Big thank-you is in order to Dosdude1, and other programmers/developers/users whose combined skills breathed new life into “apple-disowned” but very, very capable machines.
 
  • Like
Reactions: pkouame
Dosdude - thank you very much for fast reply ! Very usefull informations !

Julian - also thanks very much for help ! So, the main solution is to set transparency off, as i done up to now, great !
As you mentioned, there are still glitches present. Are this glitches/ errors restricting the user in work / making work impossible, or are they just "cosmetics" which are sometimes in some situations present ?

Thank you !

Most if not all of the current Mojave glitches on supported and unsupported devices are purely cosmetic.
 
  • Like
Reactions: TimothyR734
I´m one of the lucky guys who bricked an Air 2,1 with the ROM patcher. Have been in contact with another one who had this outcome. So it´s at least three.
But I have to say it worked as a charm on a bunch of other of my machines (home & office!). So I´m not sure it was just bad luck with the MBA 2,1 or it is system specific failure of the ROM patcher?

I missed this your message even if was settled just before mine, but I wanna be straightforward, if I had read it before attempting firmware patching, I would have tried the ROM Patcher anyway, since I wanted APFS of an external USB disk to show up in MBA2,1 startup manager. And if I took the risk it's because I did not really care for it. The weird thing is that everything seemed went fine. I think I will throw away 20$ for an A1304 EFI CHIP 820-2375-A, since even in 2018 those logic board are still very expensive, and some selling them at cheaper price I am almost sure that are simply reflowed.
This machine was factory defective.
 
  • Like
Reactions: TimothyR734
I missed this your message even if was settled just before mine, but I wanna be straightforward, if I had read it before attempting firmware patching, I would have tried the ROM Patcher anyway, since I wanted APFS of an external USB disk to show up in MBA2,1 startup manager. And if I took the risk it's because I did not really care for it. The weird thing is that everything seemed went fine. I think I will throw away 20$ for an A1304 EFI CHIP 820-2375-A, since even in 2018 those logic board are still very expensive, and some selling them at cheaper price I am almost sure that are simply reflowed.
This machine was factory defective.

If it’s not useful as a computer anymore then you can still use it as a paperweight or something.
 
It’s not necessary. You can run Mojave on a Hard Drive with no problems especially on machines with SATA III. It will be a little slow but it is definitely still fast.
Unfortunately im using MacBook with SATA II bus with SATA III drive and top speed of SIII drive on SII is 160MB Read/100Write.
 
Sharing an installation experience.

Successful installation of Mojave, up to developer beta4, with full iSight camera functionality, on
Macbook Pro 5,2 - mid 2009, Core2duo 3.06 MHz, 8 MB of RAM, hybrid Seagate HD (with APFS format)


I installed Mojave beta with first reiteration of dosdude1’s Mojave patcher, using a 16 GB USB stick, and steps identical to installing High Sierra. Mojave was installed on top of High Sierra 10.13.6 (beta version at the time).

First reboot, after installation, caused laptop to continually reboot. I pressed option key, after second loop, and this “brought up” the screen listing the drives/volumes available. I chose the USB stick, and booted back into the patcher, launched “post install patcher,” selected my computer model from dropdown menu, and re-patched the drive.

Reboot proceed smoothly, until a document appeared on the screen, and a dialog box with a warning, that “installation could not complete…” and “offering” a selection of action choices, including “restart.”

I restated with option key pressed, and chose once more to boot into the USB drive, and launched post-install patcher. This time I checked “force cash rebuild” function, and then “reboot.”

The installation went without a hitch, and I was greeted with login screen.

The system was slow for a length of time; activity monitor showed many processes that are invoked by new system installation, ie, system optimization, indexing, etc.

All system functions were available, except the iSight camera, and few other minor glitches (already reported by others), including lack of “dynamic desktop” function. I did have full graphic acceleration on both Nvidia 9600M GT and the 9400M cards. System was visibly more responsive than HS.

Subsequent developer betas were installed using Apple’s download utility. Installing this utility launches the software update utility, located in system preference panel, which then links to actual download file.

Latest developer beta (18A336e) did require patching, due to recurring booting loop. Pressing option key to interrupt the “looping”, then booting back into the USB stick, activating post install patcher, and re-patching, fixed the issue and update fully installed.

The latest developer Beta–4 fixed “dynamic desktop” function, but the iSight camera still did not work.

Using guidelines from posters here, I extracted from High Sierra 10.13.5 installer the IOUSBHostFamily.kext and IOUSBFamily.kext, and “placed” them on Mojave desktop. Then, I downloaded an application “KextBeast,” and followed instruction within it, to install the two kexts into Mojave’s system/Library/extensions folder.

*Warning,* as noted by other posters here, just moving the kexts into the Mojave’s system extensions folder will not work, unless set of specific terminal commands are executed afterward. KextBeast app. is just one of several applications, which can properly install those Kext items. If a restart is attempted without the above Kext processing, computer will boot into the login screen, but the cursor will be “frozen,” because all USB devices (including external ports) will be disabled.

Following replacement of Kexts, a restart resulted in boot-looping. So, again, I used option key to boot back into the USB stick, launched the patcher, re-patched, rebooted, and was greeted by login screen.

Once logged in, I found the iSight camera worked perfectly, without any apparent collateral damage.

Currently the System is very fast, and stable. The CPU idles at > 97% ( up to 98%), when no applications are engaged, other than Activity Monitor.

Big thank-you is in order to Dosdude1, and other programmers/developers/users whose combined skills breathed new life into “apple-disowned” but very, very capable machines.
Excellent feedback! Thanks for sharing your experience at length. We all benefit from these successes and failures. By the way, I haven't found a kext "utility" yet that doesn't boot loop... so I prefer manual installations or of course @dosdude1 's latest post install with cache rebuild turned ON. Question: is your iSight now permanently fixed/functional ? I may try this when time permits.
 
  • Like
Reactions: TimothyR734
I've noticed the "Desktop and ScreenSaver" preference pane will take a long time to load, and display a pinwheel, when I first launch System Preferences. After it's been launched you can Show All and then it will load just fine, but then relaunching the app and opening that pane will take a while again. Anyone else getting this?

Also when you drag a disk to the trash on the desktop, in Light mode the Eject Icon looks normal, but if on dark mode it looks like the old Eject icon (like in 10.9 and below). This has nothing to do with Unsupported Macs but I just thought of pointing this out. Is it supposed to be like this?
Z6nbeJW.png
WbiLjDp.png
 
Anyone having issues getting continuity working on current or last beta? It worked on first beta after I used The continuity activation tool. I am on the new public beta and I am unable to get it to work after using activation tool? Any one having similar problem?
 
  • Like
Reactions: TimothyR734
I use switchresx since long time ago to get more colors in resolution, and find it still workful in Mojave b4.
 

Attachments

  • Screen Shot 2018-07-19 at 7.49.26 PM.png
    Screen Shot 2018-07-19 at 7.49.26 PM.png
    2.9 MB · Views: 164
  • Like
Reactions: TimothyR734
Unfortunately im using MacBook with SATA II bus with SATA III drive and top speed of SIII drive on SII is 160MB Read/100Write.
With SSD on SATA III I think you should be getting speeds much better than that. This on 2 different iMac's, 1w/ SATA II, the other SATA III. in System Report what is "Negotiated Link Speed" under SATA/SATA Express?
EDIT;
I may have misread your post, I thought you had an SSD
 

Attachments

  • SATA II.png
    SATA II.png
    290.5 KB · Views: 179
  • SATA III.png
    SATA III.png
    255.6 KB · Views: 115
Last edited:
I've noticed the "Desktop and ScreenSaver" preference pane will take a long time to load, and display a pinwheel, when I first launch System Preferences. After it's been launched you can Show All and then it will load just fine, but then relaunching the app and opening that pane will take a while again. Anyone else getting this?

Also when you drag a disk to the trash on the desktop, in Light mode the Eject Icon looks normal, but if on dark mode it looks like the old Eject icon (like in 10.9 and below). This has nothing to do with Unsupported Macs but I just thought of pointing this out. Is it supposed to be like this?

If you are on Mojave beta 4 18A336e, then same side effects maybe of patching maybe of beta, I guess Dynamic Wallpaper new panel eats more resources, and for instance I preferred 10.9 icons/dock styles. And I know cDock, the tweaks are omnipresent.
 
  • Like
Reactions: TimothyR734
Excellent feedback! Thanks for sharing your experience at length. We all benefit from these successes and failures. By the way, I haven't found a kext "utility" yet that doesn't boot loop... so I prefer manual installations or of course @dosdude1 's latest post install with cache rebuild turned ON. Question: is your iSight now permanently fixed/functional ? I may try this when time permits.
Let me know if it works for you if you use kextbeast I tried and followed the instructions I rebooted constant boot loop then hit option click my macOS Mojave Patcher usb it went into a endless reboot loop turn off my iMac 8,1 then plugged my external hard drive with Sierra installed was able to boot into that then switched to another macOS Mojave patcher usb reinstalled all post install patches still the reboot loop so now doing a clean install of Mojave
 
Thanks @webg3 my iSight camera works just fine now!

@pkouame Yes I've upgraded to dev beta 4 and after replacing those 5 kexts my iSight seems to work consistently, tested with multiple app (skype, FaceTime, PhotoBooth, even QuickTime..). But I didn't noticed any difference in video/image quality, it's just like it was with High Sierra. I'll do a comparison just in case.

I'm on a MBP 7,1 (mid 2010)
 
  • Like
Reactions: jackluke
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.