I think it better fits here as the original question is from this thread here and I could also boot 12.0.1 with FileVault 2 (the info that I now use 11.6.1 was purely additional).You might want to post your comment on the Big Sur thread?
I think it better fits here as the original question is from this thread here and I could also boot 12.0.1 with FileVault 2 (the info that I now use 11.6.1 was purely additional).You might want to post your comment on the Big Sur thread?
The joys of T2. Earlier Macs use any SSD.
Thanks for reporting.By the way: NightRai has just posted an IMHO really helpful hint in the OCLP issues on GitHub for reviving the keyboard backlight OSD control: Read Sweater Software's free application Touché, once launched, restores keyboard backlight OSD control functionality on my MacBook Pro. I can even quit the application and the OSD control functionality (F5 / F6) remains.
Hi all,Frequent] "Volume Hash Mismatch" - Appears as a notification, not sure what it means.
That's actually not the problem. The 2015 MBP does not have a T2 chip and it can use any SSD. However, it cannot use any SSD if you want to upgrade the firmware. In that case it needs the original SSD. After the firmware has been updated, you can reinstall your third-party SSD.The joys of T2. Earlier Macs use any SSD.
Right, considering the original post was concerning a cMP patched with a non-Legacy version of OpenCore.That's actually not the problem. The 2015 MBP does not have a T2 chip and it can use any SSD. However, it cannot use any SSD if you want to upgrade the firmware. In that case it needs the original SSD. After the firmware has been updated, you can reinstall your third-party SSD.
That's obviously a real problem if you have sold or thrown away the original SSD in the meantime.
BTW, the 2015 MBP is still a supported machine for Monterey, so it really has nothing to do with the subject of this thread.
Monterey version attempted?? 12.0.1 or 12.1b1. ?Hi all,
installing on my Late2013 iMac 21´ works, but after first reboot i also get this "Volume Hash Mismatch" error.
Any solutions or workarounds? Seems to be an Apple problem - not OpenCore.
View attachment 1906390
Had to reinstall Big Sur...
Best,
JB
My Late 2013 13" MacBook Pro (MacBookPro11,1) has been giving this warning ever since I first installed OCLP on the internal EFI partition. Other than the warning there are no other issues and everything runs fine. It shows up on every version of Monterey from the early 12.0 betas through the first 12.1 beta.Hi all,
installing on my Late2013 iMac 21´ works, but after first reboot i also get this "Volume Hash Mismatch" error.
Any solutions or workarounds? Seems to be an Apple problem - not OpenCore.
View attachment 1906390
Had to reinstall Big Sur...
Best,
JB
Thanks and sorry the late reply. I tried the micro patcher but that did not work. I did put in the Apple Original Samsung ssd and had no luck but I have since used OCLP with success and am all good. Thanks!when you say samsung is that an apple original ssd or its an after market samsung? if you can do a screen shot for your ssd i can tell you if its an original or after market.
witch OS you are trying to install?
in your case your MacBook the last OS you can get (no patching) is macOS Mojave
That special case of not being able to upgrade macOS with a third-party SSD only shows up on a certain MacBook Pro.Hi everyone, new user here.
I've been following this thread for a while, trying to correlate all of the information, but I admit I'm a bit out of my league. Hopefully someone more experienced than me can provide insight.
My current machine is a Late 2012 Mac mini (6,1) running Big Sur 11.6.1 via OCLP 0.2.5 -- Everything is running absolutely great as-is. I think that my Mini came with a third-party SSD, (I purchased the machine re-certified). In System Information the model shows as "Lexar."
I do see the update for Monterey 12.0.1. But from reading this thread, I get the impression that it's impossible for me to install Monterey due to a firmware upgrade requirement being incompatible with third-party SSDs. Do I have that right?
Since everything is currently working fine on Big Sur, I'm perfectly content to maintain the "If it isn't broke, don't try to fix it" attitude, and keep rolling along. I just want to be sure that I've hit the limit of my upgrade path, and not giving up prematurely.
Thanks everyone. OCLP has been a real blessing on this 2012 Mini. It still runs phenomenally and lightning fast.
—5 Tracks.
It really is slower on boot-up than Big Sur, here on various of my intel machines. But 2min. is still too long. There might me some config. error involved, or unrecognized hardware etc.I had success with OCLP on my trusty 2012 Retina MacBook Pro 10,1 and it feels even snappier than BigSur. One problem though is a very very slow boot. Probably 2 minutes which is weird. Currently not using any encryption. I am currently away and have not tried verbos mode yet. Thought I would ask first if anyone else has experienced this and knows an easy fix. Thanks!
Will do and report back! ThanksIt really is slower on boot-up than Big Sur, here on various of my intel machines. But 2min. is still too long. There might me some config. error involved, or unrecognized hardware etc.
Boot verbose and see what it chews on for that long duration...
Your issue looks a little different then mine. I can get in safe mode and install the post Nvidia patch just fine, but once it reboots it freezes on the Apple logo.read previous posts, mine in particular as i had the same issue
Thanks for that bit of good news! I'm still slowly working up the courage to do the upgrade. ? I'll wait a bit more to see if anyone else has success jumping to Monterey on a Mini 6,1. I haven't seen any reports about my model, and wouldn't know how to restore to Big Sur without data loss if something goes sideways.That special case of not being able to upgrade macOS with a third-party SSD only shows up on a certain MacBook Pro.
Your 2012 Mac mini is very likely to contain a 2.5" SSD anyways (originally a spinning drive or fusion drive), not an M.2 type where this special problem occurred.
So, yepp, you're still able to go that "unsupported machines" road a bit further with your machine, i.e. running Monterey 12.0.1 or 12.1beta (with the RDRAND patch in OCLP 0.3.1)
Thank you sir... Still love my MBP 9,2 mid 2012 though. have a great one!Lame, such a "supported machine" ;-)
No, honestly, congrats!!