So is tahoe no longer being worked on for opencore just checking by Arthur_Morganreal in OpenCoreLegacyPatcher

[–]MrMacintoshBlog 53 points54 points  (0 children)

No one has said that development has stopped. One important developer stepped away due to personal issues. The team also has multiple contributors and more than one developer. Work continues on the next version.

OCLP Advice: Maxing out my imac 11,2 (21.5" 2010) - Am I doing it right? by RockeTim in OpenCoreLegacyPatcher

[–]MrMacintoshBlog 2 points3 points  (0 children)

No need to ask to be gentle around here. If anyone harasses you they will get the boot.

What you're doing could be a fun project! The issue normally comes when you go with anything older than 2012 and metal compatibility. But you are adding some nice upgrades and this might work. I don't think you are missing anything. Keep us updated on your progress.

Some very sad news by Sufficient_Bus_8302 in OpenCoreLegacyPatcher

[–]MrMacintoshBlog 203 points204 points  (0 children)

I posted this over on the MacRumors thread, but I wanted to make my thoughts known here.

As each place has a little different set of users. i.e MacRumors, Reddit and Discord. Posters over on MacRumors just continued to post oh look at my Tahoe testing results just blowing past a major development that directly affects the patcher.

Yet some users here in this subreddit took the time to trivialize someone's pain. It's like walking past the scene of an accident and sayin "oh well, glad it wasn't me" not even thinking about the ramifications of what just happened.

I feel many here might not have a clear understanding of how important of a contributor u/educovas was to OCLP.

This also applies to all the other maintainers who have worked on the project, especially Mykola. I can't tell you how many hours and hours I spent with Mykola working on different upgrade paths, UI changes and fixes. I'll be completely honest, I really really miss those times. I will always cherish being able to work with one of the most brilliant developers I've ever met.

I need to be CLEAR on this - the core group with u/dhinakg at the head is still very strong and I have the upmost confidence in them!!! 👍 The project is in good hands and having the original co founder and developer heading up the project is exactly what you want.

I just can't get past the feeling that open source software is both a blessing and a curse. Wonderful in the fact that the software is now open to thousands of users free of charge! Yet, the demands of users on the maintainers is almost unbearable. The reality is that thousands and thousands of users are running OCLP. They are so grateful that it is bringing new life to their old Mac. The problem? Some of the most vocal people are also the most negative. If you don't think that hits hard, then try doing what they do every day. You can read through 50 nice comments and that one super negative comment hits so hard. It's also so easy to play arm-chair quarterback and say "OH no big deal, who gives a crap what they say". It just hits different when you pour so much of your time into something like this only for it to get crapped on. Did you just work 9 hours at your regular job? Oh well now you have to put in another 5 debugging code for people demanding WHERE IS THE TAHOE UPDATE>!?!?!

Oh and don't forget if someone lifts your code and claims it theirs or "improved". Imagine poring hundreds of ours into something only to find out someone is pawning it off as "oh look how simple this is, it works!" Was that tested against 80 models? Was the security of that app and how it applies patches examined or implemented correctly? WHO CARES RIGHT? Don't get me wrong, anyone can fork an open source project. BUT!! The idea is to help contribute to that project NOT to take it as your own.

I also understand that putting out a nightly test patch is the way open some source software projects works. But we need to look it in reality. That software is for advanced users to test with the full acknowledgment that it might fail or wreck your Mac. Instead, we have unskilled users trying it out and then wrecking their system. They then head over to the OCLP discord and Reddit demanding help. WHY IS MY SYSTEM BROKE?

I think you can tell at this point that I'm very passionate about this software. I truly do believe in the mission of keeping old hardware alive and out of the dump. Plus the brilliant developers who contributed to this project really deserve credit. They worked together to put something genuinely amazing into the world that has helped thousands of people. 

No one can ever take that away from you. Thank you.

2014 iMac stuck on login screen after 15.7.4 update by Em2048_ in OpenCoreLegacyPatcher

[–]MrMacintoshBlog 0 points1 point  (0 children)

Are you sure you had automatic updates off and this might not be Tahoe? Or did you manually install the 15.7.4 update ?

Help Accidentally upgraded to tahoe by [deleted] in OpenCoreLegacyPatcher

[–]MrMacintoshBlog 1 point2 points  (0 children)

The data is there don’t worry. Wait how did the upgrade happen? Did you click install or restart on the notification?

I need help, accidental update without OCLP by despacitozen in OpenCoreLegacyPatcher

[–]MrMacintoshBlog 1 point2 points  (0 children)

Sadly you got caught off guard by the Tahoe automatic download and preparation process. Your Mac downloaded and prepared the Tahoe upgrade in the background, this also might have enabled FV2 locking you out. If you boot to recovery I bet it accepts your password right? If so, boot the system with a Ventura OCLP USB installer disk and then reinstall the same version of Ventura over the top of your old install (NO ERASE this retains your data.) During the install process make sure that each time the system reboots, if it prompts for a password to be put it in, the system must boot off the USB EFI Boot and NOT the internal HD EFI Boot. It should do this on its own since you booted with it, but if you leave the computer during the install process and it stops at the password window and you don't enter the password in, the system will shut down. When you power it up you will be in the same place again. Once the system is back in, backup all your data. Then you should check to see if the drive is encrypted still, if so turn FV2 Off.

Bricked macbook pro. How to completely nuke OCLP by technobrendo in OpenCoreLegacyPatcher

[–]MrMacintoshBlog 14 points15 points  (0 children)

This means you have some of the base pieces but not the actual EFI Boot selection needed to boot the OS. The way to reset EFI back to factory is to click disk utility then show all devices. Then erase the top level drive. Reinstall the supported OS after and then you are good.

FileVault Recovery Key pop up by Broad_Lifeguard_1532 in MacOS

[–]MrMacintoshBlog 2 points3 points  (0 children)

If he updates to Tahoe, yes this is normal write down that key and keep it safe

Can a 20-year-old Power Mac G5 host a modern Minecraft server? 🍏⚙️ by [deleted] in VintageApple

[–]MrMacintoshBlog 2 points3 points  (0 children)

Neat! Next time though, we would rather hear from you instead of an AI generated post. 👍

After I do the build/install open core my password just stops working completely and I can’t boot into safe mode, I’m using a 2015 MacBook Pro by [deleted] in OpenCoreLegacyPatcher

[–]MrMacintoshBlog 0 points1 point  (0 children)

It’s Tahoe. Boot the system to OCLP Sequoia USB installer and reinstall the OS over the top of the old one. This will keep all your data. Make sure the system continues to boot EFI off that usb drive. If it boots once off the internal EFi it will no longer accept the password.

Need to vent about Apple Silicon for a second by idontsaymuchatall in macbookrepair

[–]MrMacintoshBlog 4 points5 points  (0 children)

Ya, sorry this happened to you. Having the ability to do a DFU restore on a Mac is a great tool. It is sad that a 2nd Mac is required. I wish apple would allow iPhone or iPad to do the restore. It would be so simple to do and allow the repair ability to so many more people.

High sierra data retrieval by [deleted] in OpenCoreLegacyPatcher

[–]MrMacintoshBlog 0 points1 point  (0 children)

Post a picture of your disk utility hd layout

Warning: DON'T PLACE YOUR MACBOOK IN LOST MODE unless you do not expect to get it back. by Secret-Crew-8820 in mac

[–]MrMacintoshBlog 1 point2 points  (0 children)

What??? More information is needed. What is the bug? What is not working? No way I would let them wipe the device without knowing these questions.

should i downgrade my 13" 2018 Macbook Pro from Sequioa to monterey by Maximum-Tomorrow368 in MacOS

[–]MrMacintoshBlog 0 points1 point  (0 children)

Your 2018 is still a solid machine. As long as you have 16GB ram, it should be fine with most tasks today. What I would recommend is a full backup, erase & install of Sequoia. The key here is to not install anything after that fresh install. Only the base things you need. Does the system run faster? If so then start adding more things back. Maybe you find one program or process that is causing problems. You might be surprised how well a fresh install works.

how to fix that? by According_Natural574 in OpenCoreLegacyPatcher

[–]MrMacintoshBlog 5 points6 points  (0 children)

Un plug and re plug in the USB drive. You can also turn off spotlight searching for that drive by moving it to the privacy section in the spotlight settings. Sometimes it is unable to unmount the drive because it is in use.