Is anyone down to help me out with the thunderbolt route. I'm willing to pay (apologize if that offends anyone) but I'm just a total noob. Just really afraid of somehow making a mistake on one of the steps and then having to do a complete wipe of my computer. Definitely willing to pay someone who can just walk me through it step by step.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Help! Updated to macOS 10.12.4, MBP randomly shuts off
- Thread starter mokhan23
- Start date
- Sort by reaction score
Okay, after reading the posts over and over again, I feel like I might actually be able to do it myself lol. As big of a noob as this sounds, what's the best method of figuring out my MacOSDrive name where I need to input for terminal code? I've listed down below the different names I have and just not sure which that needs to be inputted:
Booted up terminal on desktop: Aryas-MacBook-Pro:~ AV (shown in picture "AV")
Cmd + R terminal: Macintosh HD - Data (shown in picture 2)
Once you guys help out with my noob question, do you mind filling in the blank of with the example below of how I should type it into the terminal once going through the recovery mode terminal?
mount -uw /Volumes/__________
Very last question, enable csrutil at the very end of everything or just leave it disabled?
- sincerely, the big noob
Booted up terminal on desktop: Aryas-MacBook-Pro:~ AV (shown in picture "AV")
Cmd + R terminal: Macintosh HD - Data (shown in picture 2)
Once you guys help out with my noob question, do you mind filling in the blank of with the example below of how I should type it into the terminal once going through the recovery mode terminal?
mount -uw /Volumes/__________
Very last question, enable csrutil at the very end of everything or just leave it disabled?
- sincerely, the big noob
Attachments
Last edited:
Update:
Went ahead and stopped being scared (lol) and did the changes. Appreciate the reply @naguzmans!
I accidentally renamed the first two .bak files as ".BAK" and did the rest in ".bak" (image attached). Assuming the capital letters shouldn't be an issue since it's an extension? If it is an issue, assuming I just go back into cmd + r terminal and run through the same exact process/steps (without the csrutil disable/csrutil auth disable steps since they're implemented?) and just change the files from ".BAK" to ".bak"?
Appreciate the patience with my questions.
Went ahead and stopped being scared (lol) and did the changes. Appreciate the reply @naguzmans!
I accidentally renamed the first two .bak files as ".BAK" and did the rest in ".bak" (image attached). Assuming the capital letters shouldn't be an issue since it's an extension? If it is an issue, assuming I just go back into cmd + r terminal and run through the same exact process/steps (without the csrutil disable/csrutil auth disable steps since they're implemented?) and just change the files from ".BAK" to ".bak"?
Appreciate the patience with my questions.
It is not an issue, you just have to rename them, leave it that way.
So, I'll wait too much for your SSD and suppose you'll receive a positive results
No update yet. I had planned on performing the SSD upgrade over the Thanksgiving break. Unfortunately, my SSD didn't arrive until Monday after Thanksgiving and I haven't had a minute to get to it yet. Honestly, I'm not expecting it to help with the crashes. If I had to guess, I'd give it less than 1 and 10 chance of working.
Hey, I know this is a little off-topic but relates to the Big Sur update (let me know if you want me to delete the comment and post in a different thread) but has anyone experienced choppiness/quick spikes of lag while typing or moving/using any application windows? Seems like a ton of people are having issues (even with reset of smc/pram). Never had any issues with performance in the prior OS and I believe my MB has internals compatible with big sur.
Has anyone experienced the same issue(s) and have found a remedy for the fix?
Has anyone experienced the same issue(s) and have found a remedy for the fix?
So, I'll wait too much for your SSD and suppose you'll receive a positive results
I'm happy to report that so far after upgrading my SSD, I've been running for 8 hours, 32 minutes without a crash or restart. And with working Thunderbolt ports!
I can hardly believe it! For the first time in more than 18 months, I finally have a MacBook that doesn't crash AND has working Thunderbolt ports AND doesn't need a silly Python script spinning in a busy-wait loop.
I know it's still a little early to declare success, but so far so good. This is incredible. With a $300 SSD upgrade kit, I not only got my MacBook working again, I also have twice the storage space. For those interested, I purchased the Aura Pro X2 1.0TB Solid-state Drive from OWC. The install was quick an easy (and I'm no good with hardware, trust me). I used Carbon Copy Cloner to transfer the data from the original SSD to the new one, which had to ran overnight to complete the transfer.
The only downside so far, is that I swear it takes slightly longer to boot now (45-50 seconds vs 30 seconds on the original SSD). But overall performance and speed is good once booted.
There are probably less expensive SSDs out there, but I've had good results with OWC in the past and I wanted a faster SSD with the transfer kit and enclosure.
30 hours without a crash or reboot. I'm still running macOS Catalina 10.15.7. I'll upgrade to the 10.15.7 Supplemental Update this weekend. I'm staying away from Big Sur for now.
in my case. no random shutdowns since 16NOV with BigSur 11.0.1. Perfectly!
€: MBP late 2013
€: MBP late 2013
Wow! Can you please clarify if you've renamed/moved the Thunderbolt drivers on your MacBook since upgrading to Big Sur? Do you have working Thunderbolt ports?
Hopefully last noob question: I'm wanting to upgrade from Big Sur 11.01 to 11.1 (hoping it fixes the lag/spike issues people have been experiencing). Does the .kext rewrite process need to be applied again with minor updates or is it only with major updates that it usually needs to be applied?
Thanks for your patience with the questions
Thanks for your patience with the questions
All updates do a system integrity check, and replace the missing extensions. Likely to make sure updates don't fail.
This update looks like it's mostly for airpods and M1 related stuff. You might consider skipping it.
This update looks like it's mostly for airpods and M1 related stuff. You might consider skipping it.
I'm in a similar situation. I completed all the steps without issue AND I never re-enabled csrutil. I typed reboot, then got stuck in a restart loop. Currently reinstalling Big Sur.
Any ideas what happened here? (I'll grab photos next time going through the process)
I am having the same issues with my MacBook Pro (Retina, 15-inch, Late 2013). I am running Big Sur 11.0.1.
My solution has been to use an external monitor. Unfortunately that not so easy while on a train... So I am
looking for a proper solution. I have found my way here but I'm getting lost in all the different posts in this
thread. Can someone point me to the right place please.
Thanks!
My solution has been to use an external monitor. Unfortunately that not so easy while on a train... So I am
looking for a proper solution. I have found my way here but I'm getting lost in all the different posts in this
thread. Can someone point me to the right place please.
Thanks!
I went through the steps outlined by naguzmans. But, like I said, still got stuck in a restart loop. I have noticed a few odd things with the random shut downs, however. They have not occurred on Zoom calls, or while watching netflix. They have not occurred while running heavy software like final cut pro or logic pro. For the past two days I have left logic pro projects open while I do other work and there has not been any shut downs. It's not a long term solution, but its working for me until I can give naguzmans solution another try.
Without the fix you should not have any shutdowns while stressing the CPU... I think you did not apply the fix correctly.
After months of frustration, finally utilized the Python script, and it worked! BUT, being a total noob, didn't know how to run and execute a Python script automatically, so used the guy who created a little app that does the same thing, for $10. It keeps one of my CPU cores at about 10-14% usage, and everything has been working! SO grateful -- even though it's a hack, if it works, it works, and is unobtrusive.
Using a late 2013 MBP, 2.3 quad i7, Big Sur.
Here's the link to MBP Random Shutdown Fix from Real Mac Mods. Once you install and run the app, add it to your login items and you're good to go. You'll see a process in Activity Monitor called "Python" and it hovers around 10-14% of CPU usage.
After 5 Apple calls and a drop-off for repair where Apple claimed to fix it (but didn't), I have little hope Apple will ever offer a solution for our "legacy" products, but this works!
Using a late 2013 MBP, 2.3 quad i7, Big Sur.
Here's the link to MBP Random Shutdown Fix from Real Mac Mods. Once you install and run the app, add it to your login items and you're good to go. You'll see a process in Activity Monitor called "Python" and it hovers around 10-14% of CPU usage.
After 5 Apple calls and a drop-off for repair where Apple claimed to fix it (but didn't), I have little hope Apple will ever offer a solution for our "legacy" products, but this works!
This is in line with observations made by others. Apparently, when the CPU is taxed the problem does not occur. This is the reason that apps and scripts which put the CPU into an endless spin loop make the symptom go away. (Albeit, at the expense of taking up 6-15% of the CPU and potentially draining the battery faster.)
@jparm1 recently pointed this out here:
Help! Updated to macOS 10.12.4, MBP randomly shuts off
After months of frustration, finally utilized the Python script, and it worked! BUT, being a total noob, didn't know how to run and execute a Python script automatically, so used the guy who created a little app that does the same thing, for $10. It keeps one of my CPU cores at about 10-14%...
forums.macrumors.com
There's a Pythons script that has been posted multiple times in this forum which does the same thing as the $10 app. It's also possible to automate the Python script using Automator for free instead of paying for the app:
Effortlessly Automate Your Python Scripts!
Ever wish your Python Scripts could just automatically run?
Others have noted that upgrading the SSD also makes this problem go away, which is what I ultimately did.
Removing the Thunderbolt drivers also has worked in previous versions of macOS (not sure about Big Sur) at the expense of not being able to use Thunderbolt ports and devices.
Update: For an example of the Python script with details see this earlier post:
Help! Updated to macOS 10.12.4, MBP randomly shuts off
Sorry to hear that @Watchman314. Have you tried the Python/busy-wait loop trick to keep the processor busy? I can't find a link to the Python code, but below this is what worked for me. You'll need to copy the code into a file and name it something like mbnocrash.py: #!/usr/bin/env python...
forums.macrumors.com
Last edited:
In previous osx versions I've only had to rename the AppleThunderboltNHI.kext file. And it's the same with Big Sur for myself. I only renamed NHI.kext and it's no longer shutting off all the time.
I was wondering if anyone could explain what the kmutil and bless commands are doing? And if they're even necessary? I notice that the bless snapshot in Disk Utility is using up around 15gb of space.
Just asking because for High-Sierra, Mojave and Catalina I've only had to rename the NHI.kext file to fix this issue.
I am also wondering about details for this. I'm no expert but after some investigation, I believe it has to do with additional protections in Big Sur around protecting the system boot volume and creating a snapshot after making changes.
I was able to find these references but not super helpful:
Protecting data at multiple layers - Discover - Apple Developer
Apple devices have multiple encryption features to safeguard the system and people’s data. Some capabilities are enabled by default, and developers only need to be aware of them in rare cases. Other features, such as Data Protection, can benefit from explicit design decisions to select the best...
Does anyone else have more details about how the
kmutil and bless commands work in the linked post above?
Big Sur boot volume layout
Detailed account of disk, volume and folder layouts on Big Sur’s boot disks, complete with roadmaps which are downloadable as PDFs.
eclecticlight.co
Can anyone help me please. I have tried 3 methods but I don't understand how to rename the kext, how am I supposed to do the exception?
Is there a video tutorial or something? Or at least a tutorial with pictures command per command
| - mv AllThunderboltKexts.kext AllThunderboltKexts.kext.bak (Except IOThunderboltFamily.kext) |
Is there a video tutorial or something? Or at least a tutorial with pictures command per command
The exception is just a comment and AllThunderboltKexts means the list of Thunderbolt related kexts (as shown in some screenshots)