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.
Thanks, in the meantime I found the solution myself (which is build OC and run the patches from the terminal, just for the record)
 
Very easy upgrade to Sequoia 15.7. Applying non-metal NVidia Tesla and Brcm Wi-Fi post-install patches with OCLP 2.4.1. Posting this with Safari Version 26.0 (20622.1.22.118.2).

About This Mac
Screenshot 2025-09-17 at 10.33.40 AM.png
 
Updated MBP10,2, MBA6,2, MBP14,3 successfully to 15.7. Only MBA6,2 got stuck in the update process. Had to go via safe mode. Now everything (Microsoft Auto-updater doesn't count) seems to work well.
About the MBA6,2: I've got the same model running Sonoma 14.8. I may try an OTA update to 15.7. Can you tell me how you used safe mode in your update process?
 
Hey all, could someone please help me fix this error? I can't use drag and drop to the desktop from other applications. I always get this message. The last time I did drag and drop was under Monterey. I think it was the specific image I was trying to drag and drop. Other things are working as expected now. However, I will still leave this question open as I'm not sure why the specific image I was dragging out of messages to the desktop would have done this.
Screenshot 2025-09-17 at 12.54.06 PM.png
 
Last edited:
Hey all, could someone please help me fix this error? I can't use drag and drop to the desktop from other applications. I always get this message. The last time I did drag and drop was under Monterey. I think it was the specific image I was trying to drag and drop. Other things are working as expected now. However, I will still leave this question open as I'm not sure why the specific image I was dragging out of messages to the desktop would have done this.
View attachment 2550746
Looks like the image file name is that big long '.' separated string... and starts with a '.' ... '.' (dot) files are invisible in the Finder by default. Command + Shift + '.' to see hidden, invisible files in Finder.
 
  • Like
Reactions: paalb
Looks like the image file name is that big long '.' separated string... and starts with a '.' ... '.' (dot) files are invisible in the Finder by default. Command + Shift + '.' to see hidden, invisible files in Finder.
I had shared the image I generated in Gemini on the iPhone directly to messages via the share sheet, is it possible Google named it something Finder doesn't like? This was done in iOS, was just accessing the message on the mac to save the image.
 
The installation of 15.7 went surprisingly smoothly, considering my recent experience with MP6.1 and Sequoia. Of course, KDK in 15.6. I just have one question: why do I see the Apple logo in 4K only during installation, and then only a huge apple pops up? Is this a bug or my wrong settings? Is it because I am using a UGREEN 8K@60Hz Displayport KVM Switch? I know, I know, it's only a cosmetic ‘problem’, but I'm curious why this is happening.
 

Attachments

  • IMG_6733.JPG
    IMG_6733.JPG
    352 KB · Views: 19
About the MBA6,2: I've got the same model running Sonoma 14.8. I may try an OTA update to 15.7. Can you tell me how you used safe mode in your update process?
I booted into safe mode and the update process that had got stuck continued. Then I reverted the root patches and started again. After that everything went well, as far as I remember it...
 
  • Like
Reactions: ronton3
I have a question about a point upgrade using OCLP. I have OCLP installed on an MBA running Sonoma. Because of that I have an OCLP EFI partition installed on the internal SSD. When I create a USB installer for Sequoia using OCLP, do I then build and install an OCLP EFI partition on the USB drive? The documentation isn't clear about that. I added it to the external USB drive, but when I reboot holding the option key, unsurprisingly I have two EFI icons to choose between. Do I need to choose the EFI partition on the USB drive or the SSD, or should I rebuild the USB installer without an EFI partition?
 
Last edited:
When I create a USB installer for Sequoia using OCLP, do I then build and install an CLP EFI partition on the USB drive? The documentation isn't clear about that.
Yes. See the bottom of the following docs page.
Do I need to choose the EFI partition on the USB drive or the SSD, or should I rebuild the USB installer without an EFI partition?
Choose the EFI partition on the USB drive... then choose the macOS Sequoia Installer.
 
  • Like
Reactions: ronton3 and dogen
late 2015 iMac here, upgraded to 15.7 OTA using OCLP 3.0.0 nightly without issue.

any word on how the 2014 Mac mini is doing with the 15.7 update using OCLP 3.0.0?
 
Yes. See the bottom of the following docs page.

Choose the EFI partition on the USB drive... then choose the macOS Sequoia Installer.
I've never done that, has always worked for me without. Does it make a difference whether the EFI is internal or external? Obviously you need to create it on the USB before you start using OCLP, but once it is on your internal drive, OS updates work flawlessly. But of course it works the way, Bigwaff suggests. YMMV...
 
For those who are interested and whom this is useful to:

Now and then bluetooth is acting up on my machine. Paste this into an AppleScript, save as application and you can restart bluetooth services in one go.

do shell script

"sudo defaults write /Library/Preferences/com.apple.Bluetooth ControllerPowerState -int 0 &&
sudo killall -HUP bluetoothd && sleep 2 &&
sudo defaults write /Library/Preferences/com.apple.Bluetooth ControllerPowerState -int 1 &&
sudo killall -HUP bluetoothd"

with administrator privileges
 
For those who are interested and whom this is useful to:

Now and then bluetooth is acting up on my machine. Paste this into an AppleScript, save as application and you can restart bluetooth services in one go.

do shell script

"sudo defaults write /Library/Preferences/com.apple.Bluetooth ControllerPowerState -int 0 &&
sudo killall -HUP bluetoothd && sleep 2 &&
sudo defaults write /Library/Preferences/com.apple.Bluetooth ControllerPowerState -int 1 &&
sudo killall -HUP bluetoothd"

with administrator privileges
Very useful, thanks; the above won't compile in Script Editor, this will:

do shell script "defaults write /Library/Preferences/com.apple.Bluetooth ControllerPowerState -int 0; killall -HUP bluetoothd; sleep 2; defaults write /Library/Preferences/com.apple.Bluetooth ControllerPowerState -int 1; killall -HUP bluetoothd" with administrator privileges
 
I updated the following machines from Sequoia 15.6 or 15.6.1 to 15.7:

iMac 2011 27“, i7 2600, 24GB, 1 TB, K2100m
iMac 2011 27“, i7 2600, 16GB, 1 TB, K2100m
iMac 2011 21,5“, i7 2600s, 20GB, 1 TB, K2100m
MBP 2015 13“, i5, 8GB, 256GB
MBP Early 2013 13“, i5, 8GB, 256GB

All updates went smooth and without any error. All machines were already on OCLP 2.4.1. Created separate installer sticks with OCLP for each and started the installation from Mac OS. Root patches were applied automatically after installation. After the updates, Spotlight needed some time for indexing. All seem to run flawlessly so far and are rather snappy. I used this script to prevent Tahoe updates to appear for 90 days.
 
Looks as if the upgrade from 14.8 to 15.7 is stuck in a later part of the installation. The MBA had rebooted from the internal drive after installing from the OCLP-created USB drive, and the progress bar shows about 40% completion (no estimated time, just the Apple logo and progress bar), but it doesn’t seem to have progressed for about 30 minutes.

Should I assume the upgrade completed but got stuck rebooting, and therefore force a restart in safe mode from the internal disk and install OCLP root patches from there? Is it better to give it a few hours and see if the progress bar advances?
 
Should I assume the upgrade completed but got stuck rebooting, and therefore force a restart in safe mode from the internal disk and install OCLP root patches from there? Is it better to give it a few hours and see if the progress bar advances?
I would reboot into safe mode and proceed from there. Seen and done that many times. Good luck.
 
Good afternoon.
MacAir 2012 13" (5,2) with a problem upgrading from 15.6.1 to 15.7.
I always use the OCLP procedures with a USB installer.
This time, well into the install process, it stopped with this dialog box:1.jpeg
After clinking the 'OK', I had this dialog box underneath:
2.jpeg
Haven't seen this before, so I waited about 45 minutes to see if anything would happen. Nothing.
So, as many of you would have told me, I powered down, wait about 15 seconds, and powered her back up.
It went back to the MACOS installer and started again. But with about 15 minutes left, it again stopped with the same two dialog boxes.
Has anyone see this before and possibly a fix.
Thank you in advance,
Jim
 
Good afternoon.
MacAir 2012 13" (5,2) with a problem upgrading from 15.6.1 to 15.7.
I always use the OCLP procedures with a USB installer.
This time, well into the install process, it stopped with this dialog box:View attachment 2554787
After clinking the 'OK', I had this dialog box underneath:
View attachment 2554792
Haven't seen this before, so I waited about 45 minutes to see if anything would happen. Nothing.
So, as many of you would have told me, I powered down, wait about 15 seconds, and powered her back up.
It went back to the MACOS installer and started again. But with about 15 minutes left, it again stopped with the same two dialog boxes.
Has anyone see this before and possibly a fix.
Thank you in advance,
Jim
It's not known what causes this, therefore no known fix either. The only way that is known is to just keep rebooting into 'macOS Installer' until it ultimately goes through.
 
I had a similar problem, and I couldn't even start the update when the update from 15.6.1 to 15.7 arrived. After 10-15 attempts, I finally succeeded. The same error occurred during the update. I didn't reboot, I just clicked OK, and then everything went white on the screen. I assumed the drivers had crashed, and the update worked without any lag. The update was successful. After the update, OCLP 2.4.1 launched automatically and asked me to patch it.
 
Last edited:
It's not known what causes this, therefore no known fix either. The only way that is known is to just keep rebooting into 'macOS Installer' until it ultimately goes through.
Seen this many time also. What has helped here is to delete all the partitions affected in Disk Utility and then create a new one to install to. It seemed to me that the installer can sometimes get "confused/stuck" when preparing the update.
Ah well. FWIW and not empirically deep-tested but might perhaps be worth your while if you get stuck.
 
Last edited:
OCLP and Migration Assistant do NOT play nicely. Macbook 9,1 with fresh Sequoia 15.6 install.
Time Machine disk from M1 MBA running 15.6.
Used Mgration Assistant to migrate ONLY User folder from TM disk, but NOT system files, applications or anythinge else.
Result: Boot loop after migration completed - sigh
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.