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.
~ DP8 and the equivalent PB7 ~

Aloha Folks!

Is Apple releasing both at the same time now? I have 2 scenarios that I need update testing on:
  1. Developer Preview on an APFS.
  2. Public Beta on an HFS+ partition.
~ Mahalo ~

Is Public Beta 7 out yet? I did not see it listed in the OP. (only DP8 is included). Thanks.
 
  • Like
Reactions: TimothyR734
Thank you for the help. The machine is booting in verbose mode, but the keyboard is not recognize. In order to check is not some hardware problem I booted my High Sierra partition holding CMD+S. In this case the keyboard is working.

I then simply open a terminal an moved to the directory UserEventPlugins. There is no com.apple.telemetry.plugin file.

Code:
cd /Volumes/Mojave/System/Library/UserEventPlugins/
sudo ls *telemetry*
ls: *telemetry*: No such file or directory

If you already have telemetry removed, but still have keyboard not recognized with system loop reboot in your Mojave, then follow this tip, it should work, from your High Sierra copy/replace all the 5 (they are five) IOUSB***.kexts into your Mojave /System/Library/Extensions/

Then open High Sierra Terminal and type:

sudo chmod -R 755 /Volumes/Mojave/System/Library/Extensions
sudo chown -R 0:0 /Volumes/Mojave/System/Library/Extensions
sudo touch /Volumes/Mojave/System/System/Library/Extensions
sudo kextcache -u /Volumes/Mojave
sudo reboot

You should have a couple of Mojave reboot then it should boot normally.


if still not work, after replaced all the 5 IOUSB from HS try this:

Boot from Mojave USB Installer, select Post Install, choose you Mac Model, but this time de-select any patch related to USB, and last most important select "Force rebuild cache"

After done boot from your Mojave holding CMD+S then type:

fsck -fy
mount -uw /
chown -R 0:0 /System/Library/Extensions
chmod -R 755 /System/Library/Extensions
kextcache -i /
reboot
 
Last edited:
  • Like
Reactions: TimothyR734
Just updated to Beta 7 from the Software Update and then repatched with the older USB stick.

What frightens me is that with the Intel HD3000 this laptop is almost unusable.
 
  • Like
Reactions: TimothyR734
Safe mode didn't work for me either and I tried your approach and I got this while trying to safe boot:
View attachment 777052

Same here. Same message and not working

Try this, boot Mojave normally then from Terminal type:

sudo nvram boot-args="-v -no_compat_check -x"

It should not give more unsupported machine on Safe Mode, but remember from safe mode Terminal to type again:

sudo nvram boot-args="-v -no_compat_check"
 
  • Like
Reactions: TimothyR734
I just noticed something when I updated my iMac 9,1 I still have dashboard when my usb hdd with High Sierra bailed on me I found a spare 320gb formatted APFS installed DP8 and choose light mode and noticed dashboard is missing and it is missing on my MacBook 5,2 as well but it is formatted HFS and installed DP8 over DP7 I did find it in the applications Folder just thought was strange used to seeing it right next to mission control in launchpad :)
 
Last edited:
Good news! After installing DP8 on an empty APFS drive, running post install, the computer booted onto the APFS drive! Not going to risk my main drive, but I will keep this partition around until the next update rolls out to test the native updater. I have no idea what changed, but I got Mojave installed and booted on an APFS drive!
Screen Shot 2018-08-21 at 12.43.51 PM.png


Also, the EFI Boot option is back, going to go through the mounting process and see if I can get rid of it.
 
Last edited:
Well done—now you KNOW the APFS boot ROM patch IS working!
Perhaps the problem is something to do with the old Hitachi HDD and having had mixed HFS+ and APFS partitions on it previously—perhaps a corrupted partition map but that's a wild guess.
Get a SSD to replace that spinning rust—it will feel three times faster in the GUI.
 
Well done—now you KNOW the APFS boot ROM patch IS working!
Perhaps the problem is something to do with the old Hitachi HDD and having had mixed HFS+ and APFS partitions on it previously—perhaps a corrupted partition map but that's a wild guess.
Get a SSD to replace that spinning rust—it will feel three times faster in the GUI.

It’s running mixed right now, 2 HFS+ and 1 APFS. About a week ago I erased the Hitachi itself to get rid of any left over disk space or corrupted containers that laid around. No idea what fixed it, but maybe it was just DP7.
 
  • Like
Reactions: TimothyR734
In DP7 onwards Apple has revamped the Reduce Transparency colouring. Light mode looks much better with white colours instead of grey colours. I fully support this aesthetic change and it makes the pain of these transparency issues much better. This probably looks better with a lighter wallpaper as mine has quite a contrast with light mode.

Dark Mode with Reduce Transparency.png Light Mode with Reduce Transparency.png
[doublepost=1534883938][/doublepost]Here it is with light and dark wallpapers.

Dark Mode with Reduce Transparency and Dark Wallpaper.png Dark Mode with Reduce Transparency and Light Wallpaper.png Light Mode with Reduce Transparency and Dark Wallpaper.png Light Mode with Reduce Transparency and Light Wallpaper.png
 
In DP7 onwards Apple has revamped the Reduce Transparency colouring. Light mode looks much better with white colours instead of grey colours. I fully support this aesthetic change and it makes the pain of these transparency issues much better. This probably looks better with a lighter wallpaper as mine has quite a contrast with light mode.

View attachment 777090 View attachment 777091
[doublepost=1534883938][/doublepost]Here it is with light and dark wallpapers.

View attachment 777093 View attachment 777094 View attachment 777095 View attachment 777096
It does look better in light mode in safe mode there is a bit more transparency in dark mode
 
  • Like
Reactions: pkouame
It does look better in light mode in safe mode there is a bit more transparency in dark mode

Transparency is fine in dark mode but small anomalies like artifacting on window borders exist. The problem is when you use applications that either don’t have a dark mode or that have parts that don’t have a dark mode because they look bad if Reduce Transparency is off even in dark mode.
 
Transparency is fine in dark mode but small anomalies like artifacting on window borders exist. The problem is when you use applications that either don’t have a dark mode or that have parts that don’t have a dark mode because they look bad if Reduce Transparency is off even in dark mode.
I got my highlight color set to graphite so no more tinting in light mode
 
  • Like
Reactions: pkouame
EEPROM Programmer arrived today and detect/program the desoldered EFI CHIP A1304 has perfectly working, correctly writing back the "MacBookAir2,1_backup.bin" taken by "APFS ROM Patcher", but unluckily after soldering again the EFI CHIP on logic board hasn't worked, same behavior of a bricked EFI CHIP, maybe a corrupted previous backup on wrong chip type or too hot air in desoldering/soldering, with a friend's help tried to check schematics on some SMD resistors, but apparently they were fine, I guess no more chances to fix my old MBA.
 

Attachments

  • 820-2375.pdf
    1.3 MB · Views: 447
  • EEPROM programmer MX chip efi id.PNG
    EEPROM programmer MX chip efi id.PNG
    59.2 KB · Views: 140
Last edited:
Try this, boot Mojave normally then from Terminal type:

sudo nvram boot-args="-v -no_compat_check -x"

It should not give more unsupported machine on Safe Mode, but remember from safe mode Terminal to type again:

sudo nvram boot-args="-v -no_compat_check"
No go for me, Unsupported OS, reboots to Verbose and restarts to SUM & on it own running fsck -f. string of errors and restarts into Login, I login (which I'm Auto login) here's the weird part, no more UI glitches, ie trails.

My Bad Safe Boot. Without UI glitches
 
Last edited:
@Luckygreek: You don't have OpenGL as well ?
opengl extensions viewer tells
[doublepost=1534888222][/doublepost]did some more testing, today an Apple HD5770 in my Mac Pro 3.1 test box

glitches = trails when dragging windows

dp4, no openGL, no glitches

dp7, no open GL, glitches
dp7 safe boot, no open GL, no glitches

dp8, no open GL, glitches
dp8 safeboot, no open GL, no glitches


I was a little dumb with my HD4870, as this is a supported GPU has open GL drivers, run benchmarks, cinebench and so on.

AMD5/6 has no open GL. But anyway, some (what I call) framebuffer acceleration.

those glitches must been some rendering changes, now computed on the (openGL / Metal unsupported) GPU.
 
Last edited:
[QUOTE"Once you have eliminated the impossible, whatever remains, however improbable, must be the truth." — Spock, Star Trek
[/QUOTE]
An aside. I think that quote belongs to Arthur Conan Doyle's character Sherlock Holmes, in his books written in the late 19th Century. Predates Star Trek quite a bit...
 
No go for me, Unsupported OS, reboots to Verbose and restarts to SUM & on it own running fsck -f. string of errors and restarts into Login, I login (which I'm Auto login) here's the weird part, no more UI glitches, ie trails??????

WTF??

I'm not sure I've understood, it's a good (or bad) sign?

I guess with "-x" parameter you have booted in safe mode, so that's why you have less glitches apparently, without OpenGL.

edit:
No, I'm wrong, @Macschrauber is right, on safe mode you cannot have framebuffer acceleration.

Without at least framebuffer acceleration MacOS is almost unusable.
 
Jackluke, you're on to something as I get no UI glitches in any app in Safe Boot. Also system font is different, appears it dropped a point or 2.


EDIT
I ran into this once before DP5, every restart or boot up it goes in Verbose and restarts after a string of errors.

ran sudo nvram boot-args="-v -no_compat_check"
Restart
back into Verbose.
Booted from USB and ran patch, restart, goes back into Verbose
back with trails.
 

Attachments

  • Normal.jpg
    Normal.jpg
    168.3 KB · Views: 130
  • Safe Boot.jpg
    Safe Boot.jpg
    137.5 KB · Views: 125
Last edited:
@dosdude1

Is there a way to implement in the Post Install App that unchecking a patch the patcher removes the patch ?

I am into testing what causes the trails. I now reinstall with almost no patches. It would be easier if the patcher removes a patch when unchecking.
 
Jackluke, you're on to something as I get no UI glitches in any app in Safe Boot. Also system font is different, appears it dropped a point or 2.

I don't notice any differences in your pictures, anyway safe mode is the slowest MacOS you could have, better using normal boot with unload GPU kext or at least leaving only Framebuffer partial acceleration w/o OpenGL.

The dropped points in safari are or ⌘+ / ⌘- or a lower screen resolution.
 
Last edited:
I ran into this once before DP5, every restart or boot up it goes in Verbose and restarts after a string of errors.

ran sudo nvram boot-args="-v -no_compat_check"
Restart
back into Verbose.
Booted from USB and ran patch, restart, goes back into Verbose & back with trails.
I don't notice any differences in your pictures, anyway safe mode is the slowest MacOS you could have, better using normal boot with unload GPU kext or at least leaving only Framebuffer partial acceleration w/o OpenGL.

The dropped points in safari are or ⌘+ / ⌘- or a lower screen resolution.

I didn't make any changes in resolution, text appears compressed.
[doublepost=1534890296][/doublepost]
I don't notice any differences in your pictures, anyway safe mode is the slowest MacOS you could have, better using normal boot with unload GPU kext or at least leaving only Framebuffer partial acceleration w/o OpenGL.

The dropped points in safari are or ⌘+ / ⌘- or a lower screen resolution.


Agreed, wait & see what come down the pipe, it is butt slow in safe mode.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.