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.
… Personally, anyway, I’d wait for the future Ventura AMFI (and hopefully also LV) fix: well, this might take quite some time, of course…

(BTW, as for macOS 14, Sonoma wouldn’t be a bad name, among the still many candidates:

IMG_2790.png


… but here, just an old mockup for Ventura.)
 
Last edited:
Hello,
I have installed latest Ventura on a mid 2014 MacBook Pro and everything has gone smoothly.

I only have one issue that I cannot understand if it depends on the battery health or on some OCLP settings.

If the power supply is not connected, the computer powers up but when I login, after a few seconds, it switches off.
I need to connect it to the power supply and after a few minutes, it will resume operating.

I wonder if it depends on battery on or OCLP as, once powered up, I can switch off the power adapter and it works perfectly for a few hours.

Has anyone an idea?
Thanks,
Daniele
 
  • Like
Reactions: LongWelsh
Hello,
I have installed latest Ventura on a mid 2014 MacBook Pro and everything has gone smoothly.

I only have one issue that I cannot understand if it depends on the battery health or on some OCLP settings.

If the power supply is not connected, the computer powers up but when I login, after a few seconds, it switches off.
I need to connect it to the power supply and after a few minutes, it will resume operating.

I wonder if it depends on battery on or OCLP as, once powered up, I can switch off the power adapter and it works perfectly for a few hours.

Has anyone an idea?
Thanks,
Daniele
I have the same MacBook turning off NVMe power management in OCLP Misc Settings before building OCLP worked on earlier versions for me this would depend which Ventura your using as I’m still on 13.2.1. This is no way guaranteed to make a difference I have put a SK Hynix Gold P31 1TB in it.
 
I have the same MacBook turning off NVMe power management in OCLP Misc Settings before building OCLP worked on earlier versions for me this would depend which Ventura your using as I’m still on 13.2.1. This is no way guaranteed to make a difference I have put a SK Hynix Gold P31 1TB in it.
Thanks for helping, I am on 13.3
 
Update:
The only way I'm able to install 13.2.1 on a mbp 6,1 is to install it on a drive in a cMP 5,1 and then put the drive in the mbp 6,1 and then do the oclp patch.
Cheers

P.S. Monterey installs just fine on my mbp 6,1 so i'm using it.
Both OS's are crap in a mac with no Metal.
Many apps require metal to run right!
I'll just use monterey for now on my 6,1 mbp since there are no install issues like in Ventura.
 
Last edited:
Well, there seems to be a way to do this:


… That is: after booting from the USB flash installer, open Disk Utility and erase only the System, not the Data volume; then, proceed with the macOS installation, which should leave the Data volume intact and downgrade only the System volume. In this case, there probably aren’t yet any apps that require 13.3+, so downgrading to 13.2.1 should be acceptable. Haven’t tried this: proceed at your own risk…! :)o_O
The procedure you described works, but then conflicts arise. When I tried to do this, for example, after installing macOS, Time Machine recognized a different "Macintosh HD - Data" drive than the one in its backups, as if it saw two drives, and then Time Machine refused to restore the data.
So in the end I had to format the ENTIRE drive and after installing the System from scratch, using an USB PENDrive, I restored the Data from Time Machine backup.
I think doing it this way is best
 
The procedure you described works, but then conflicts arise. When I tried to do this, for example, after installing macOS, Time Machine recognized a different "Macintosh HD - Data" drive than the one in its backups, as if it saw two drives, and then Time Machine refused to restore the data.
So in the end I had to format the ENTIRE drive and after installing the System from scratch, using an USB PENDrive, I restored the Data from Time Machine backup.
I think doing it this way is best
For me if I need to go back to a slightly older OS I use this methed since my OS drive is about 2TB of stuff and dont want to start over.
In my case I use CCC to backup.
 
photoshop stuck when open a file,Macbook 11,5 Haswell/Radeon M375X Ventura 13.4 B3,OCLP0.6.4

5 issues I meet now

1. when Photoshop open,GPU switch to Radeon M375X, it seems work so well the, startup speed even faster than my workstation PC (Ryzen 9, Windows 11), but when I open a file or create new file Photoshop just stuck,minutes later,photoshop quit automatically
i tried diff photoshop version form 24(2023)to 22(2022), still same issue It only works well when I close the GPU acceleration in ps.


2. the permisions issue,all installed app can not list them in permission lists what they need automatically,some permissions can add that manually,but contacts,camera,microphone,automation permissions need tccplus to add


3. youtube video cant play usually. most time the browser open page and play videos well, some time broken,issue disapear after restart system. I didn't know why.
hope can solved these isseus and thanks for your brilliant work, guys you did so well sorry for my poor english

4. No content when I create a new file or open a file in Adobe XD

5. No any content in Jetbrains Tools box app
 
Last edited:
The procedure you described works, but then conflicts arise. When I tried to do this, for example, after installing macOS, Time Machine recognized a different "Macintosh HD - Data" drive than the one in its backups, as if it saw two drives, and then Time Machine refused to restore the data.
So in the end I had to format the ENTIRE drive and after installing the System from scratch, using an USB PENDrive, I restored the Data from Time Machine backup.
I think doing it this way is best
Have you tried, in the Time Machine System Settings, to remove the TM disk and then re-add it…? Hopefully, then it should resume backups normally, from where it left. Probably some form of volume UUID issue, who knows…
 
Last edited:
  • Like
Reactions: OKonnel
In 13.3.1 and with the latest 0.6.5 nigthly, the rendering issues in Parallels seem to be solved, and Linux and Windows 10 VMs with the Parallels hypervisor start normally (albeit with AMFI disabled); but when starting a Windows 11 VM (with the Parallels hypervisor, too), shortly after the entire Mac freezes, and it must be force-shut down. Only with the very latest nightlies, IIRC (the first ones worked well)…
 
Have you tried, in the Time Machine System Settings, to remove the TM disk and then re-add it…? Hopefully, then it should resume backups normally, from where it left. Probably some form of volume UUID issue, who knows…
Thanks for your suggestion @Sven G that I have not tried so as not to risk it. My backup data, in fact, is valuable because it relates to my work.
So even if your idea worked, Time Machine refused to auto-restore when I went back to Ventura 13.2.1 from Ventura 13.3.1.
By formatting the entire disk, however, the recovery was successful and also all the old TM backups are still valid.
In short, I was curious too and I discovered that you can only delete the "Macintosh HD" container, as you say. However, the new System, during installation, DOES NOT recognize the previous "Macintosh HD - Data" container and creates a new one; after that, so, the restore would have to be done manually as Time Machine refuses to restore the Data.
Therefore, since there is no benefit, I think it is better and simple to format and then restore everything.
Of course it is my opinion.
 
  • Like
Reactions: Sven G and rehkram
^^^ I know, from having done it, that if you install macOS on a disk without macOS (for example, an ordinary CCC data clone), the installer recognises the user accounts on the disk and thus “merges” the existing data volume with the new system volume: as if everything had been installed together. But now you say that this doesn’t happen if you delete - or erase? - the system volume on an existing install and then reinstall macOS. Strange… Anyway, here, others will have to experiment with this, if they want to: personally, I think that now I’ll remain on 13.3.1 and wait for the fix to re-enable AMFI(/LV)…
 
Last edited:
^^^ I know, from having done it, that if you install macOS on a disk without macOS (for example, an ordinary CCC data clone), the installer recognises the user accounts on the disk and thus “merges” the existing data volume with the new system volume: as if everything had been installed together. But now you say that this doesn’t happen if you delete - or erase? - the system volume on an existing install and then reinstall macOS. Strange… Anyway, here, others will have to experiment with this, if they want to: personally, I think that now I’ll remain on 13.3.1 and wait for the fix to re-enable AMFI(/LV)…
Oh yeah... True what you say. But I had to downgrade the System (from 13.3.1 to 12.3.1) and you too know that macOS doesn't allow to overwrite the System with an older version. Sob…
 
  • Like
Reactions: Sven G
Here's a thing; the new Rapid Software Response 13.3.1(a) chokes on downloading on OCLP 0.6.5 and cMP5,1. Gets so far and then does this.
Screenshot 2023-05-01 at 19.16.16.png


And much the same thing on wife's iPad on latest iPadOS. And again on wife's MBAir...
 
Last edited:
Here's a thing; the new Rapid Software Response 13.3.1(a) chokes on downloading on OCLP 0.6.5 and cMP5,1. Gets so far and then does this.View attachment 2196159
Have seen it on an earlier occasion with an MBP5,2 when RSRs were new.
Worked just now with a supported MBP16,1.
But had the equivalent problem right now on two iPhones SE2...

EDIT:
the MBP5,2 is Penryn which explains it, because RSR doesn‘t work on pre-Haswell.
Cured itself meanwile on the iPhones.
So all normal now.
 
Last edited:
A similar problem for RSR also on iOS: must be something on Apple’s part; see the comments:



Update: it works, now…
 
Last edited:
Last edited:
I always use disk utility to clone a working OCLP volume. No need for CCC.
disk utility works very well but my os drive has almost 1.7TB's of files and apps on it and to do a complete backup via disk utility every time takes about 4 hours every time lol.
I prefer a incremental backup using ccc which takes about 15 to 20 mins max.
cheers;)
 
Last edited:
  • Like
Reactions: hvds and olad
I have installed latest Ventura on a mid 2014 MacBook Pro and everything has gone smoothly.
I have the same MacBook turning off NVMe power management in OCLP Misc Settings before building OCLP worked on earlier versions for me this would depend which Ventura your using as I’m still on 13.2.1.

Hi, I'm using also a 15" MacBook Pro 2014 (11,2) with OCLP 0.6.4 + Ventura 13.2.1– everything ok.
I tried 3 times to get Ventura 13.3.1 to work successfully but often MBP rebooted itself when I opened the TV App or App Store; 1sec before reboot the cursor move directly to left upper corner.

What are your actual experience - everything working? Which macOS and OCLP version are u using?


@TOM1211
Do I understand correctly that NVMe power management ONLY needs to be turned on when NOT using an original Apple SSD anymore?
So is it better not to tick this if you are still using the factory SSD?
 
  • Like
Reactions: macpro_mid2014
Is it really secure to install these RSR on OCLP-patched systems?
Thought I had read OCLP team suggest don't to do it...
My experience has been that any delta updates do not work on patched macOS and you need to download and install the full update. If RSR updates are delta, they will not likely work on patched macOS.
 
  • Like
Reactions: luckyduke23
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.