Sidebar Sidebar
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

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.
victor30r said:
Tardé dos días en repararlo. Cada vez que encendía el MacBook Pro solamente emitía pitidos y no se encendía. Tardé 2 días en encontrar la solución. El cd lo tuve que crear desde un equipo windows utilizando TransMac. Entonces metí el cd en el MacBook Pro, conectado a la corriente. Lo encendí y comenzó a actualizar el firmware y a funcionar con normalidad. Al ver que había podido repararlo volví a intentar con APFS Rom Patcher y esta vez funcionó todo perfectamente y ya puedo arrancar el Macbook Pro desde discos APFS de forma nativa
Click to expand...

If you used transmac it means that the CD you created is an hybrid HFS+/ISO/UDF , please could you elaborate which files do you have copied into the empty transmac's disk image before burning to an empty CD ?
It was a .pkg file or .fd file ?
But much more simply, since you already have your burned CD, insert into your MBP5,1 then open the CD from finder and take a screenshot of which files are inside the CD.

Firmware restoration CD is an Apple UDIF Media container with an HFS Mac OS extended (NOT plus/journaled) partition inside.
Only a BootROM .fd file could be recognized at low level for re-flashing an Intel Mac emergency firmware.

Anyway it remains still a mystery how you recovered a MacBookPro5,1 with a firmware restoration CD.
 
Last edited:
  • Like
Reactions: ASentientBot and TimothyR734
jackluke said:
If you used transmac it means that the CD you created is an hybrid HFS+/ISO/UDF , please could you elaborate which files do you have copied into the empty transmac's disk image before burning to an empty CD ?
It was a .pkg file or .fd file ?
But much more simply, since you already have your burned CD, insert into your MBP5,1 then open the CD from finder and take a screenshot of which files are inside the CD.

Firmware restoration CD is an Apple UDIF Media container with an HFS Mac OS extended (NOT plus/journaled) partition inside.
Only a BootROM .fd file could be recognized at low level for re-flashing an Intel Mac emergency firmware.

Anyway it remains still a mystery how you recovered a MacBookPro5,1 with a firmware restoration CD.
Click to expand...
upload_2018-8-27_16-5-34.png
 

Attachments

  • Captura de pantalla 2018-08-27 a las 16.05.04.png
    Captura de pantalla 2018-08-27 a las 16.05.04.png
    1.1 MB · Views: 126
  • Like
Reactions: TimothyR734
jackluke said:
I think also patching the AppKit.framework could be necessary to obtain transparencies in Mojave "light mode", since this framework contains many NS*** functions.

I attach the Headers source code present inside the HighSierra's Appkit framework, for some reason apple forgotten them there.
[doublepost=1535366397][/doublepost]

Yes, I've already tried, in Mojave the "Menu Bar Tint app" will not launch because an incompatibility with the AppKit.framework, and replacing with the HighSierra one will produce many WindowServer/loginwindow pid crashes.
Click to expand...
The menu bar "tint" app is a good example of styling the menu bar. Of value to those interested in "how things work" for sure. Fixing translucency will require heavier guns unfortunately ;). But thanks.
To start "hacking" CoreDisplay and other PrivateFrameworks you'll need the right headers and my trusted source is here. He keeps a pretty good archive of all the Mojave headers across all the betas. An interesting resource to spot what is changing from beta to beta.
I would also recommend Python + pyobjc for rapid development on macOS. Its best with Xcode installed but not completely necessary. Let's you quickly tap in to critical frameworks and execute some hidden functionality. It is objective-c of course, so may be distasteful to Swift aficionados.

Patching AppKit may be necessary, but I'm trying to avoid it. It's huge and since tweaking CoreDisplay features already affects Dark/Light mode functionality, I'm focusing primarily on Core and OpenGL. May be a shortcut though, holler if you find something interesting there...

Enjoy.
[doublepost=1535386892][/doublepost]What no Beta Monday? C'mon Apple we need our fix...
 
  • Like
Reactions: ASentientBot, olad, jackluke and 1 other person
pkouame said:
The menu bar "tint" app is a good example of styling the menu bar. Of value to those interested in "how things work" for sure. Fixing translucency will require heavier guns unfortunately ;). But thanks.
To start "hacking" CoreDisplay and other PrivateFrameworks you'll need the right headers and my trusted source is here. He keeps a pretty good archive of all the Mojave headers across all the betas. An interesting resource to spot what is changing from beta to beta.
I would also recommend Python + pyobjc for rapid development on macOS. Its best with Xcode installed but not completely necessary. Let's you quickly tap in to critical frameworks and execute some hidden functionality. It is objective-c of course, so may be distasteful to Swift aficionados.

Patching AppKit may be necessary, but I'm trying to avoid it. It's huge and since tweaking CoreDisplay features already affects Dark/Light mode functionality, I'm focusing primarily on Core and OpenGL. May be a shortcut though, holler if you find something interesting there...

Enjoy.
[doublepost=1535386892][/doublepost]What no Beta Monday? C'mon Apple we need our fix...
Click to expand...
Beta's usually come out after 10am on the west coast :)
 
  • Like
Reactions: jackluke
jackluke said:
You can't use the High Sierra APFS dynamic EFI script patcher for Mojave.

The only way is through APFS ROM Patcher, but as you read it's a very risky process, it may fail even on those rare cases where for many other machines has worked.

Personally I start to think that the main failing of dumping/flashing EFI EEPROM could be issue to the too fast SSD read/write speed versus a slower spinning disk, and as known safer/better is as slower you flash a firmware.

And the EEPROM dumping/flashing/writing should not be done from the last supported MacOS (El Capitan for MP3,1) but possibly from a previous pre-SIP OSX like Lion/ML/Mavericks

And another important step for some machines is to put, holding power button 20/30 sec, in blinking led firmware write mode.
Click to expand...

Thanks,

That mean i have to do a "clean install" of Mojave and after that, at my own risk, flash the Rom.

Question : is it possible to run the APFS ROM patcher under High Sierra (having before disabled the High Sierra APFS dynamic EFI script patcher ) ?

Best regards,

PJN
 
  • Like
Reactions: TimothyR734
olrik77 said:
Thanks,

That mean i have to do a "clean install" of Mojave and after that, at my own risk, flash the Rom.

Question : is it possible to run the APFS ROM patcher under High Sierra (having before disabled the High Sierra APFS dynamic EFI script patcher ) ?

Best regards,

PJN
Click to expand...

I'm the last that can give advise on APFS EEPROM patching, since I bricked, and after reprogramming correctly too hot air has damaged some 3-4 SMC resistors atom size, anyway you should be safe cause it seems your MacPro3,1 is largely APFS Patched tested, moreover you should have this not bad firmware recovery CD: https://support.apple.com/kb/DL94?locale=en_US

However I give you an advise, don't APFS patch for now, and stay HFS+ on Mojave, since it is still supported through dosdude1's Mojave Patcher USB Installer.

I use both HFS+ and APFS on different SSDs and I can say that in my personal opinion there are no remarkable performance and reliability differences from HFS+.

I would have a little reserve only using APFS strictly on PCIe NVMe SSDs.
 
Last edited:
  • Like
Reactions: TimothyR734
jackluke said:
I'm the last that can give advise on APFS EEPROM patching, since I bricked, and after reprogramming correctly too hot air has damaged some 3-4 SMC resistors atom size, anyway you should be safe cause it seems your MacPro3,1 is largely APFS Patched tested, moreover you should have this not bad firmware recovery CD: https://support.apple.com/kb/DL94?locale=en_US

However I give you an advise, don't APFS patch for now, and stay HFS+ on Mojave, since it is still supported through dosdude1's Mojave Patcher USB Installer.

I use both HFS+ and APFS on different SSDs and I can say that in my personal opinion there are no remarkable performance and reliability differences from HFS+.

I would have a little reserve only using APFS strictly on PCIe NVMe SSDs.
Click to expand...

That is a wise advice I will follow !

Thanks very very much !
 
  • Like
Reactions: jackluke and TimothyR734
TimothyR734 said:
Beta's usually come out after 10am on the west coast :)
Click to expand...
See, they were definitely just waiting for me to shout out! They must be watching us...
[doublepost=1535390660][/doublepost]
TimothyR734 said:
Its official DP9 3.27GB
Click to expand...
Again, first! Quick on the draw...

How does it feel, any glaring changes?
[doublepost=1535390720][/doublepost]
jackluke said:
My DP9 download size offered is 3,54 GB, it's weird since I'm jumping from DP6, I expected a bigger download size, anyway for me the time has come to update.
Click to expand...
I did a 6 to 8 and the size was about that too...
 
  • Like
Reactions: jackluke and TimothyR734
TimothyR734 said:
Mine is still installing went from 21 mins left to 10 min and not even quite a 3rd of the way !0 mins jumped back up to 51 mins
Click to expand...
Definitely slower on restart. I will capture the distribution on my other machine once this one completes (hopefully) Something must be up...
 
  • Like
Reactions: TimothyR734
Just an observation... if I create an encrypted, password-protected read/write dmg in Mojave, it won't open in 10.9 or any other OS/OS X version under Mavericks. I tried to open it in OS X all the way back to Tiger, but no go. This is using the (now no longer, since a new one was just released) latest beta.

Creating the same under High Sierra will allow the older versions of macOS/OS X open them.
 
  • Like
Reactions: ASentientBot, jackluke and TimothyR734
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back