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.
I meant "on the fly" inside the same internal disk from a recovery, as the script for apfs converting, without restoring any other disk image/partitions.

I know what you meant but this is probably the only method. Unfortunately this requires a “cache” volume that’s the same size as the volume that you’d like to convert. Perhaps it’s possible to make a script that resizes the APFS volume to create a small space for a new HFS one and then copies from APFS volume to the HFS one and then resizes the APFS a bit again and repeats until all data is transferred to the HFS one.
 
  • Like
Reactions: TimothyR734
Hello, im done with testing of Mac OS Mojave Beta, its slower than High Sierra. Battery is worse, MacBook is hotter, Slower Boot, After powering up machine it did twice chime(idk why?) etc. I understand that is still Beta. But i will wait until Official Version is released. If you will run Mojave on Mac.. SSD is NECESSARY.
 
  • Like
Reactions: TimothyR734
Hello, im done with testing of Mac OS Mojave Beta, its slower than High Sierra. Battery is worse, MacBook is hotter, Slower Boot, After powering up machine it did twice chime(idk why?) etc. I understand that is still Beta. But i will wait until Official Version is released. If you will run Mojave on Mac.. SSD is NECESSARY.

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.
 
[doublepost=1531988957][/doublepost]Do you need Nvidia Web Drivers if you would use a Nvidia card in a Mac Pro 3.1?
Sorry if it was already asked
Hi I am running a MacPro 3.1 with Nvidia GT 120 running very well on this old slugger just used the Legacy Nvidia updater patch in the Post Install patcher. Nvidia do not have web drivers for Mojave yet as it is in Beta of course.
 
Hi, I’ve tried to install mojave on mbp 8,1 late 2011, without sip patch, after enabling sip from recovery audio not work, not work also after rebuild kexts from patch...
The question is, how is dangerous use a operative system with sip disabled?!?
 
  • Like
Reactions: TimothyR734
I don't think I can do that. For my capabilities replacing a logic board would be more easy.

...

I gave myself explanations:
- Maybe my MBA2,1 (C2D 2,13 Ghz) had different boot rom among the world
- Patching from a lower macOS than El Capitan would have been better
- The internal SSD buffer was too fast in dumping/writing, a spinning slower hdd would be better in this

I am not sure just replacing a boot-ROM could work since the components on the logic board could have some chips/ids differences. Maybe if I provide the binary backup of my MBA2,1 to the seller could rewrite the EEPROM chip.

I can assure you this:
- it´s not different to the rest of the world, I have tried the 1,6GHz version and bricked it
- it does not depend on newer or older macOS to run the ROM Patcher, I have done this on machines running El Cap, Sierra and High Sierra. All of them patched successfully (total of around 10 MacBooks and 1 iMac), just the MB Air went sour.
- it is definitively just the 8pin serial boot flash IC and if this is replaced/restored (clip tool vs soldering, both works) the computer is up and running again - I did this with my 1,6GHz with a chip from a seller in the Netherlands.
(If you like, send me a PM and I could offer the repair for a small fee+postage+chip).
 
Hi, I’ve tried to install mojave on mbp 8,1 late 2011, without sip patch, after enabling sip from recovery audio not work, not work also after rebuild kexts from patch...
The question is, how is dangerous use a operative system with sip disabled?!?

Many will disagree this statement: but using kernel boot flag: "kext-dev-mode=1" , you should be able to boot with "invalid signature kext: allowed" and SIP enabled, provided you patched everything before with SIP disabled.

With SIP disabled, surfing many hours per day internet and downloading/using third party apps, it's dangerous.
 
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!
 

Attachments

  • Capture d’écran 2018-07-19 à 12.23.22.png
    Capture d’écran 2018-07-19 à 12.23.22.png
    2.7 MB · Views: 262
  • Capture d’écran 2018-07-19 à 12.25.05.png
    Capture d’écran 2018-07-19 à 12.25.05.png
    991 KB · Views: 211
  • Like
Reactions: TimothyR734
I can assure you this:
- it´s not different to the rest of the world, I have tried the 1,6GHz version and bricked it
- it does not depend on newer or older macOS to run the ROM Patcher, I have done this on machines running El Cap, Sierra and High Sierra. All of them patched successfully (total of around 10 MacBooks and 1 iMac), just the MB Air went sour.
- it is definitively just the 8pin serial boot flash IC and if this is replaced/restored (clip tool vs soldering, both works) the computer is up and running again - I did this with my 1,6GHz with a chip from a seller in the Netherlands.
(If you like, send me a PM and I could offer the repair for a small fee+postage+chip).

You meant Sierra, HS from a Mac supported until El Capitan, right?
Or better Sierra, HS installed on an HFS+ disk file system?
I think so.

Thanks anyway, but I have a friend of mine with a soldering station CCD LCD, I am really not sure want to repair since it suffered of RAM/GPU issues, and as I told 2 gb ram in 2018 are too few.
 
  • Like
Reactions: TimothyR734
Many will disagree this statement: but using kernel boot flag: "kext-dev-mode=1" , you should be able to boot with "invalid signature kext: allowed" and SIP enabled, provided you patched everything before with SIP disabled.

With SIP disabled, surfing many hours per day internet and downloading/using third party apps, it's dangerous.

Perfect, how I can use this solution?
 
  • Like
Reactions: TimothyR734
Perfect, how I can use this solution?

I'd wait for others opinions. You should have SIP disabled with kextcache prebuilded first and all the patches for you machine already in.
Anyway, boot from recovery, Terminal and type:
nvram boot-args="kext-dev-mode=1 -no_compat_check -v"
csrutil enable; reboot

Maybe booting in normal mode you should disable gatekeeper too from terminal:
sudo spctl --master-enable (disable instead of enable)
But that features is to enforce malwares defenses so leaving enabled is a better choice.

edit:

No, I am very confused in these days, I got wrong, kext-dev-mode=1 has been overrided since SIP introduction.

If can't boot go back to recovery and type: csrutil disable
 
Last edited:
Is it just me or Mojave is way Faster than high Sierra? My MBP 2011 is flying now!
Hello My MacBook Pro late 2011 with macOS mojave public beta 3 is flying too
[doublepost=1532000616][/doublepost]
Is it just me or Mojave is way Faster than high Sierra? My MBP 2011 is flying now!
Hello My MacBook Pro late 2011 with macOS mojave public beta 3 is flying too
 
  • No metal
  • No web drivers to fall back on
We can try kextloading, but that still wouldn't solve the Metal issue (missing) so at best only OpenGL apps will run accelerated, at worst the kext doesn't even load. Then we deal with whether WindowServer has any opengl code left, and if it doesn't, no UI acceleration.


But this means, that a Macbook Pro from 2010 with a Nvidia Card (330m) that supports at least Metal V1, and can fall back on the Nvidia Web driver has in fact a great chance to run Mojave ? (Maybe even greater then a AMD gpu driven machine that is a full year newer..)
 
  • Like
Reactions: TimothyR734
Hi I am running a MacPro 3.1 with Nvidia GT 120 running very well on this old slugger just used the Legacy Nvidia updater patch in the Post Install patcher. Nvidia do not have web drivers for Mojave yet as it is in Beta of course.
How would you compare it to HS on 3,1? Performance wise.
 
  • Like
Reactions: TimothyR734
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!
 
  • Like
Reactions: TimothyR734
I'd wait for others opinions. You should have SIP disabled with kextcache prebuilded first and all the patches for you machine already in.
Anyway, boot from recovery, Terminal and type:
nvram boot-args="kext-dev-mode=1 -no_compat_check -v"
csrutil enable; reboot

Maybe booting in normal mode you should disable gatekeeper too from terminal:
sudo spctl --master-enable (disable instead of enable)
But that features is to enforce malwares defenses so leaving enabled is a better choice.

edit:

No, I am very confused in these days, I got wrong, kext-dev-mode=1 has been overrided since SIP introduction.

If can't boot go back to recovery and type: csrutil disable

I use my MacBook daily as an Administrator with System Integrity Protection and GateKeeper completely disabled. I just love the freedom of being able to change any setting, delete any file, or do anything else that I want to do with my computer.
 
To all 2011 Thunderbolt mac users running the new Mojave:

@mac_4eva created a few script to enable the use of eGPU's.
These have proven to work on 10.13.4 up to 10.14 beta4 (on Mojave supported mac's)

I myself took it on me to make an installer for these scripts and an easy acces tool to use them.
ALLn1

If you have an eGPU please give it a try!
I don't think Thunderbolt 1 has enough bandwidth to drive the Mac's internal display. It's too bad as this might be a practical solution for 2011 iMacs / MBPs otherwise.
 
Many will disagree this statement: but using kernel boot flag: "kext-dev-mode=1" , you should be able to boot with "invalid signature kext: allowed" and SIP enabled, provided you patched everything before with SIP disabled.

With SIP disabled, surfing many hours per day internet and downloading/using third party apps, it's dangerous.
I always thought you had to have SIP disabled to run a patched macOS on a unsupported Mac
[doublepost=1532013567][/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!
are you signed up with Apple beta software program, if not you could sign up and download the beta software profile that should give you the lastest beta
 
  • Like
Reactions: olad
Is it just me or Mojave is way Faster than high Sierra? My MBP 2011 is flying now!
My 13" mid 2010 MBP is so much faster running Mojave latest beta 4, already ditch High Sierra yesterday, of course none of this will not be possible without the excellent work from Dosdude1.
 
  • Like
Reactions: TimothyR734
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!

Hi - You're not getting seed updates because your (internal) software update catalog is not setup correctly to receive them (by default). I triggered my system preferences upgrade to dev b4 from "patcher" b3 by doing the following:

  1. Backup any important stuff
  2. Change your software update catalog by enrolling for the Developer Seed (either run the apple seed utility from the command line or use a utility)
  3. Trigger the system preferences update and it will start downloading Apple's patch automatically
  4. Let it restart and install as suggested - takes a little while and you will end up with the blocked apple logo - you're not finished so ...
  5. IMPORTANT: run @dosdude1 's Post Install (from usb) on the proper volume. Make sure you have the latest version of @dosdude1's patcher. I had an old b9 and it did not work well on an upgraded dev b4. The version I used was patcher b12 (there may be some newer ones since)
This worked for me on mbp 5,3. Your mileage may vary, but it's all running well.

Hope this helps.
 
  • Like
Reactions: TimothyR734
I always thought you had to have SIP disabled to run a patched macOS on a unsupported Mac
[doublepost=1532013567][/doublepost] are you signed up with Apple beta software program, if not you could sign up and download the beta software profile that should give you the lastest beta

Hi, I'm not signed for dev beta, so I must install a Public Beta.
Thanks.
[doublepost=1532016706][/doublepost]
Hi - You're not getting seed updates because your (internal) software update catalog is not setup correctly to receive them (by default). I triggered my system preferences upgrade to dev b4 from "patcher" b3 by doing the following:

  1. Backup any important stuff
  2. Change your software update catalog by enrolling for the Developer Seed (either run the apple seed utility from the command line or use a utility)
  3. Trigger the system preferences update and it will start downloading Apple's patch automatically
  4. Let it restart and install as suggested - takes a little while and you will end up with the blocked apple logo - you're not finished so ...
  5. IMPORTANT: run @dosdude1 's Post Install (from usb) on the proper volume. Make sure you have the latest version of @dosdude1's patcher. I had an old b9 and it did not work well on an upgraded dev b4. The version I used was patcher b12 (there may be some newer ones since)
This worked for me on mbp 5,3. Your mileage may vary, but it's all running well.

Hope this helps.

Thanks, I'll do that! :)
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.