Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
OCLP does it for me too. But it requires an internet connection to download the latest KDK. Since I needed to apply the patches to regain network access and couldn't download the correct version, it just reused the already present 14.0 KDK, which caused the system to hang on the next boot. On a fresh system without the KDK already present, things might go more smoothly. But I was upgrading from 14.0 using a USB installer and ran into the issues I mentioned.
Ah, OK, was thinking of OTA upgrade. Might just try it and see what happens!
 
The .1 releases have always been much better than the initial release.

Not sure how many people remember this, but High Sierra had a massive bug at launch where you could gain full root access by entering "root" as username with no password on any authorization window. That was still in the OS until a security patch for .1.
High Sierra launch was so terrible, I purchased a Dell XPS 13" and boxed my Mac mini
Mojave was a vast improvement.
 
The .1 releases have always been much better than the initial release.

Not sure how many people remember this, but High Sierra had a massive bug at launch where you could gain full root access by entering "root" as username with no password on any authorization window. That was still in the OS until a security patch for .1.
Even everyone's favorite Snow Leopard was ridden with serious bugs until like 10.6.4. 10.6 and 10.6.1 had a bug that would treat the main account as guest account and delete all of a user's files. People today seem to think that a buggy .0 release is something new, but it's practically a tradition at this point.
 
  • Wow
Reactions: TheShortTimer
Well, like I said there has been problems installing 14.0 -> 14.1 update where the update does not complete and you end up with black screen or other non boot situation. And its weird, some encounter the problem and others do not. Even people with silicon macs might have the problem. It might straighten up with a safe boot or might not. I think there was some other things to try in the MrMacintosh video I posted earlier. So, it might be risky at this point if one is not able or willing to tinker with it further.

In any case a backup or even cloned drive is a good option before trying it. I personally run CCC backups daily so its easy to go back to previous state if update fails. But still I choose to wait.

Well it worked well to a point. Bluietooth remained resolutely switched off. So, back to HS, then patch to Catalina and live with it.
Did you remember to reset the nvram after the update and patching? Bluetooth was non operational originally with many of us after installing OCLP+14.0 and it was fixed with cmd+alt+p+r. Could be the same thing with later versions too.
 
  • Like
Reactions: DCBassman
Did you remember to reset the nvram after the update and patching? Bluetooth was non operational originally with many of us after installing OCLP+14.0 and it was fixed with cmd+alt+p+r. Could be the same thing with later versions too.
Nope, I obviously haven't read up enough! Anyhow, blown it away and going to Catalina for now.
I did check the system info, and the BT was there, turned off and with no address. Maybe I'll try again by OCLP-ing straight to 14.1 from HS, and clearing NVRAM!
 
Last edited:
I thought high sierra was a great OS, much better than Sierra. I used it for well over 5 years as my sole OS!
in 2018 I finished a freelance outdoor real estate photo project
using a Nikon D500 with a nice fast flash drive, sandisk™.

After plopping that in the macMini 2012 8GB_ram using high Sierra, the spinning ball occurred forever, crashing the Mac mini where I had to unplug the thing. I placed the photo card onto an adopter and finished th task on a 2010 4 GB ramMacBook Air Mountain Lion which edit the phots fine, not problems. While I used the MBair, I rebooted erased and installed mountain lion and ran that for over a year until someone persuaded me to use Mojave which was too late and did all my editing and career things on a Dell XPS 9370.
Dangs you high Sierras!

but this march I installed that on the MacBook Air
and everything works like a charm.....I even crated a post about that here!
so maybe
High Sierra needs a hug?
 
I've used High Sierra daily on my 2009 and 2011 iMacs from the beginning all the way to couple of weeks ago. Never had any OS-related problems. Didn't even remember there was some bug-o-rama in the early days. I don't think it affected me.
 
Nope, I obviously haven't read up enough! Anyhow, blown it away and going to Catalina for now.
I did check the system info, and the BT was there, turned off and with no address. Maybe I'll try again by OCLP-ing straight to 14.1 from HS, and clearing NVRAM!
Now doing a "clean" install of 14.1 over a fresh but fully updated HS install.
I'll be back...
 
I did that because I'd already installed HS due to the BT problem, having forgotten the PRAM clear. If this is problematic, it will be a true clean install next.
 
  • Like
Reactions: ToniCH
You are so quick in your moves, minor problem and you are starting from scratch. You must have reinstalled your couple of machines dozen or more times in last few weeks. ;)
 
  • Like
Reactions: DCBassman
Nothing better to do! :D
Try troubleshooting, that will keep you busy for awhile! ;)

This video seems quite straightforward on how to fix the OCLP+14.1 no boot -problem in couple of different ways. I think I'll try it with my non critical test bed iMac 27" (2011 i5, non metal GPU) today and see how it goes. I'll choose the download KDK manually -method (ie. no network connection after OS-update -scenario ).

 
Last edited:
  • Like
Reactions: DCBassman
Mr Macintosh has very thorough How to OCLP videos as well.
he is a regular here and is credited with patching on the dortana website.

when the OCLP dust has settled, I have a daunting question,
how does a blank ssd know that can install Monterey on a MBP 2012?
did the download and install of the patcher on the previous OS prompt that drive to perform the task?
this was the dosdude formula with Mojave and Catalina.
 
Mr Macintosh has very thorough How to OCLP videos as well.
he is a regular here and is credited with patching on the dortana website.
Yes, I've posted his videos to this thread about OCLP within couple of weeks, and you commented on one of those posts.

how does a blank ssd know that can install Monterey on a MBP 2012?
did the download and install of the patcher on the previous OS prompt that drive to perform the task?
Sorry, don't understand your question.

I did install Sonoma to MBP 2012 empty drive volume but the whole SSD was not blank as it has two bootable volumes with other OS versions already (10.11.6 & 10.15.7). I just booted from the OCLP Sonoma USB-stick and installed normally.
 
Last edited:
  • Like
Reactions: MBAir2010
Well, I did install the 14.1 update to my test bed iMac. Surprisingly it went quite smoothly as I didn't encounter the no boot -situation at all.

If it was pure luck or something - I don't know. Here is what I did before 14.1 update: updated OCLP to 1.1 and ran patches. Then I downloaded the KDK and left it on the desktop.

After the installation (took maybe 45+ minutes) the iMac booted several times and then ended up to blank white desktop with no backround pic. The wifi was not working as expected. I then ran and installed the KDK and ran OCLP and root patched again. And then reboot. And now everything seems to work again!
 

Attachments

  • 1st boot after oclp 14-1 update.jpg
    1st boot after oclp 14-1 update.jpg
    24.1 KB · Views: 61
  • Rootpatching.jpg
    Rootpatching.jpg
    66.1 KB · Views: 60
  • 14-1 update done.jpg
    14-1 update done.jpg
    26.1 KB · Views: 54
From my experience with the iMac I felt brave enough to try to update my MBP 2012 which also runs OCLP + Sonoma. Not a critical Mac either. Did everything like I did with the iMac but this time something was different.

1. this time the installation got stuck 🧐
2. did what the guy in video above instructed (boot to Sonoma recovery, mount volume, bless volume etc.) and then rebooted, still stuck at the same place 😨
3. did it again thinking maybe I made a mistake (there were no errors though) but no help, still stuck 😰
4. then remembered that some have managed to get unstuck by booting into safe mode, did that
5. managed to get into login window, after logging in installation continued for few minutes until I was able to log in again, machine still in safe mode :D
6. installed the KDK, ran OCLP and root patches, reboot - success!

Now it works again. After first complete boot Spotlight was super active and hogged all CPU power. Entered into Spotlight preferences and removed most of the selected options, Spotlight calmed down.

Now some testing but initially seems to work like before. 🙂
 
Last edited:
oh yeah?, I‘ll out bid yee!


They overprice these on eBay so they don’t lose their rankings and position.

several,years ago i asked a vendor about the outrageous price quest.
 
  • Like
Reactions: Jack Neill
Ordered yet another cheap Netac SSD and plopped it in my neglected 08 macbook. Gave it a fresh install of snow leopard, installed squid proxy and my most used software. It boots insanely fast and no apps beach ball on launch. I dig it. Oh, and i gave it the Pear mod including the boot logo.

snow-ssd.png
 
Can you please explain briefly the use and benefit of the Squid proxy? I've never used it and thought its some kind of server side utility. Can it cache web content for use in the client side machine?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.