codedil wrote:
Until now I was little uncertain/skeptical that if it had asked me for it and had i enabled it. But now that there is confirmation, I am mostly certain that i wouldn't have enabled it explicitly. Now that makes me question again - what is this 'Activate Mac' screen that i am seeing/stuck with ? What's the guarantee that i will not be presented with this say if i choose to go ahead with the erase mac option ?
I doubt you can erase your Mac due to that "Activate Mac" screen. Are you not seeing that as you boot into Recovery Mode?
I think you will need to perform a DFU Firmware Restore which will reset the security enclave chip, system firmware, and internal SSD (destroying all data on the internal SSD) as well as pushing a clean copy of macOS onto the internal SSD (M-series Macs only......Intel Macs you will need to then reinstall macOS through Internet Recovery Mode). You can first try a DFU Firmware Revive which resets the security enclave chip and system firmware....it should leave the data on the internal SSD intact as long as the process completes successfully.
Unfortunately the DFU Firmware Restore requires access to another Mac currently running macOS 15.x Sequoia (once macOS 26 Tahoe is released, then a Mac running Tahoe will be required). The instructions must be followed exactly in order to put the "broken" Mac into DFU Mode.
If the DFU Firmware Restore fails to apply or does not fix the problem, then most likely there is a hardware issue with the Logic Board on your laptop.
Firstly, there is still no clarity why I have ended up here - is it because of the filevault ? is it because of something else ? ( to repeat what i did : all i did was to follow the 'resetpassword' instructions in recovery mode because i wasn't getting the reset options in login window )
There are multiple things that could cause an issue like this....no I'm not sure exactly what those things could be. If the OS has an issue....usually with the admin user account, or an issue with the security enclave chip, then you may encounter this issue. With the Intel Macs with the T2 security chip, I have seen multiple instances where it was impossible to authenticate to the T2 security enclave chip even though macOS itself was still able to boot normally.
You have to keep in mind that the security enclave chip is the heart of the 2018+ Macs. The security enclave chip has ties to all a lot of the hardware to make it extremely difficult for any nefarious people to access the data on your Mac. This does have the downside of making things more difficult for the regular user as well and it also makes it more likely that something will go wrong. If the security information within the security enclave becomes corrupt or damaged, then it can become impossible to authenticate. This is also complicated by requiring at least one macOS admin user account being active & accessible.
You think the "resetpassword" caused the problem. Perhaps the login issue which required you to reset the password is actually where the problem began, but you just didn't know it at the time thinking you had forgotten the password. If there was an actual issue with logging into your macOS user account during a normal boot, then that same issue may be why you are encountering the "Activate Mac" screen because something went wrong with the macOS admin user account and/or the security enclave chip.
FYI, it is nearly impossible to figure out what went wrong. Partly due to the enhanced privacy & security features of these 2018+ Macs, and partly due to macOS itself which does not lend itself to troubleshooting these types of issues.....plus Apple doesn't really provide enough low level details on the whole security enclave implementation & authentication.
You may want to consider keeping a second macOS admin user account on your system.
And make sure you always have frequent and regular backups since there is usually no way to recover data from the internal SSD of the recent Macs due to all of the hardware, software, and security changes even if a professional data recovery service is used.
I still feel this defenitely needs some digging or at least an explanation from Apple side. But i am just not able to find a way how to do that. No way to appraoch them. It's frustrating.
You will not get such an explanation. Apple does not like communicating with users, plus there really is no way to know what happened here. The best you will get are the contributors' best guesses about what may have occurred here.
The best you can do is leave product feedback here (hard to say if this is a hardware issue or a software issue....may be a bit of both):
Product Feedback - Apple
And contacting Apple corporate to let them know about your experience with this incident and your dissatisfaction:
Contact - How to Contact Us - Apple