This is what has worked for me as well. Do you know the impact of not enabling SIP?Damn...!! Hard luck..even after doing it all.. thunderbolt drivers are still being loaded... and shut down is still happening ????
Ok Guys So Here’s the FIX with BIG SUR
I did few modifications with whatever was available on internet to solve this problem
Step 6 & 7 are few modifications which I did.
Here it goes
Reboot in recovery mode (CMD+R)
- Utilities -> Terminal
- csrutil disable
- csrutil authenticated-root disable
- mount - uw /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)
- cd /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/Extensions
- rm -rf AppleThunderboltNHI.kext
- rm -rf /System/Library/Caches/*
- Kmutil install -u --force --volume-root /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/Extensions
- bless -folder /Volumes/Macos(Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/CoreServices —bootefi --create-snapshot
FORGET THE PROBLEM :-D
You’ll need to perform these steps every time you update Big sur with their security updates n all.
No need to enable SIP
Have a good life
SIP is a security feature that prevents modification of system files. It's one level of protection against malware.Do you know the impact of not enabling SIP?
I recommend you, please read my method again. Carefully read it. I am using big sur on my mbp 2014... and haven't experienced shut down after that. My method works 100% ... tried and tested two timesI did what sodhi07 recommended, and it didn't work. My mac still shut down after a few minutes.
So I went back into recovery mode and renamed all the AppleThunderbolt and IOThunderbolt files to ".bak" files.
STILL DOESN'T WORK.
Any thoughts?
Don't restart. Go on to step 4 even though csrutil tells you to restart.Hello there, i am new to the community and i have this problem too, i dont have much knowledge about Terminal stuff but maybe you could help me out fixing the problem.
1. Reboot in rescue mode (reboot while "Cmd + R")
2. csrutil disable
3. csrutil authenticated-root disable
Theese Steps went well so far, i restarted as needed and loged into my Admin Account. I opened the Terminal and tried following.
I recommend you, please read my method again. Carefully read it. I am using big sur on my mbp 2014... and haven't experienced shut down after that. My method works 100% ... tried and tested two times
You are doing it totally wrong :|yea But still i got told to mount my harddrive "Daten" but there is no Daten>System/Library/Extensions/AppleThunderboltNHI.kext its under Apple SSD SM0512F>System/Library/Extensions/AppleThunderboltNHI.kext to find but i cant mount the Apple SSD SM0512F
like u see on the screenshot and even if i dont reboot i get the error on trying to mount it View attachment 1675629
View attachment 1675630
it still tells me i only have read persmissions. Something needs to be wrong, maybe u can find a misstake on the screenshot :/
I can find the file under Daten/Volumes/Apple SSD SM0512F/System/Library/Extensions/AppleThunderboltNHI.kext but then i am back to daten and i get the Error that i got Read only permissions.
what exactly you tried to do ? please shareI carefully followed the steps, and even after rebooting, I confirmed by going to Terminal and listing the contents of /System/Library/Extensions that the AppleThunderboltNHI.kext (and the others I deleted) are NOT THERE.
I have a mid-2014 MacBook pro, and this fix has always worked for me before. I don't know why it's not working with Big Sur?!
Also, as others have noted, as long as I have my external monitor hooked up, my MacBook doesn't crash.
Hi there,Damn...!! Hard luck..even after doing it all.. thunderbolt drivers are still being loaded... and shut down is still happening ????
Ok Guys So Here’s the FIX with BIG SUR
I did few modifications with whatever was available on internet to solve this problem
Step 6 & 7 are few modifications which I did.
Here it goes
Reboot in recovery mode (CMD+R)
- Utilities -> Terminal
- csrutil disable
- csrutil authenticated-root disable
- mount - uw /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)
- cd /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/Extensions
- rm -rf AppleThunderboltNHI.kext
- rm -rf /System/Library/Caches/*
- Kmutil install -u --force --volume-root /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/Extensions
- bless -folder /Volumes/Macos(Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/CoreServices —bootefi --create-snapshot
FORGET THE PROBLEM :-D
You’ll need to perform these steps every time you update Big sur with their security updates n all.
No need to enable SIP
Have a good life
This is exactly my situation!!!Hi there,
running MBP mid 2014 and habing the same issues. Lived with that -delete nhi routine- for years and now went for big sur. Big mistake ?
I followed each and every step of your guide. I even double checked that all those kexts are deleted from my volume.
When I boot into normal mode after that and check in /System/Library/Extensions I can confirm: no AppleThunderboltNHI.
But kextstats still show that it‘s loaded and the random shutdowns still occur.
As if those kexts were loaded from some other place.
Is there any way to confirm the kmutil or bless did it right? Like checking the correct snapshot is chosen at boot?
MiO
Hey, my email is laszlonemeth.photography@googlemail.comYou are doing it totally wrong :|
Share your email id ... let me help you out
So I have followed this excellent guide, but even with SIP and Authenticated root disabled, I can't delete the kext. I can't do it in recovery or with sudo or in a root enabled account. Clearly I'm missing something...Damn...!! Hard luck..even after doing it all.. thunderbolt drivers are still being loaded... and shut down is still happening ????
Ok Guys So Here’s the FIX with BIG SUR
I did few modifications with whatever was available on internet to solve this problem
Step 6 & 7 are few modifications which I did.
Here it goes
Reboot in recovery mode (CMD+R)
- Utilities -> Terminal
- csrutil disable
- csrutil authenticated-root disable
- mount - uw /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)
- cd /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/Extensions
- rm -rf AppleThunderboltNHI.kext
- rm -rf /System/Library/Caches/*
- Kmutil install -u --force --volume-root /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/Extensions
- bless -folder /Volumes/Macos(Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/CoreServices —bootefi --create-snapshot
FORGET THE PROBLEM :-D
You’ll need to perform these steps every time you update Big sur with their security updates n all.
No need to enable SIP
Have a good life
Hi! I followed every step that you recommend, yet on the final step (bless...) I get this message for some reason:Damn...!! Hard luck..even after doing it all.. thunderbolt drivers are still being loaded... and shut down is still happening ????
Ok Guys So Here’s the FIX with BIG SUR
I did few modifications with whatever was available on internet to solve this problem
Step 6 & 7 are few modifications which I did.
Here it goes
Reboot in recovery mode (CMD+R)
- Utilities -> Terminal
- csrutil disable
- csrutil authenticated-root disable
- mount - uw /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)
- cd /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/Extensions
- rm -rf AppleThunderboltNHI.kext
- rm -rf /System/Library/Caches/*
- Kmutil install -u --force --volume-root /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/Extensions
- bless -folder /Volumes/Macos(Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/CoreServices —bootefi --create-snapshot
FORGET THE PROBLEM :-D
You’ll need to perform these steps every time you update Big sur with their security updates n all.
No need to enable SIP
Have a good life
do this, it works after restart from recovery mode for 1 times. A restart from the working systems runs in a reboot loop:Reboot in recovery mode (CMD+R)
- Utilities -> Terminal
- csrutil disable
- csrutil authenticated-root disable
- mount - uw /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)
- cd /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/Extensions
- rm -rf AppleThunderboltNHI.kext
- rm -rf /System/Library/Caches/*
- Kmutil install -u --force --volume-root /Volumes/Macos (Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/Extensions
- bless -folder /Volumes/Macos(Enter WHATEVER YOUR MACOS DRIVE NAME IS, my macOS drive name is Macos)/System/Library/CoreServices —bootefi --create-snapshot
I think it's the same for me too.This is exactly my situation!!!
Yes, I finally got 11.1 installed after incredible problems. Took 3 downloads of the software from the Apple server. The download I did and the upgrade, (which happened inadvertently by the way), bricked the Mac. Consistently failed and took me 24 hours to get the machine back. Quite frankly I don't even know what I did except kept downloading and reinstalling Big Sur until it worked. The machine is working OK, but that old problem is still there with shutting down. Apple really needs to come up with a fix for this, or perhaps they are waiting for next year when they tell us our machines are redundant. If the new M1s work OK then I'll be upgrading anyway.Are we going to have to do the lather, rinse, repeat every time? Now that 11.1 is out has anyone experienced the shutdown?