boot chime fix didn't work

Question

Level 2

201 points

boot chime fix didn't work

Hi, I have a new late 2016 15 inch MacBook Pro with Touch Bar. As most know, Apple chose to remove the classic boot chime on start up. There is, however, a widely described nvram command that is supposed to turn it back on. That command is

sudo nvram BootAudio=%01

Many have reported that it works. I tried it and it did NOT work. I did it more than once. I then went ahead and did the nvram command to shut it back off which is that same as above but with %00. Just to try to be sure I put things back where they were initially.

I saw hints that perhaps Apple had changed the firmware on the newest of these new MacBook Pro's yet again, thus disabling even the above command.

Can anyone shed any light on this??? Is the classic Apple boot chime recoverable on these newest MacBook Pro's or not??? I think there are a few things Apple should really leave as is and that chime is one of them. I've heard why they decided to do it. I just disagree.

Does anyone know what gives on why the above command did nothing on my machine???

thanks

MacBook Pro with Retina display, macOS Sierra (10.12.2), late 2016 model with Touch Bar

Posted on Jan 12, 2017 11:36 PM

Reply

Answer 1

Robert Paris Author

Level 2

201 points

Feb 19, 2017 8:56 PM in response to billwood09

Seems like I saw somewhere (though I don't recall where as it's been a few weeks now) that someone was saying this capability might NOT work on the very newest Macs with the very newest Firmware. I bought my new MacBookPro on January 9th, 2017, so just over a month ago. nvram edit did nothing on mine. Maybe someone else has something to add???

Yes, I too, disabled auto boot as a trial and instead of booting the computer, when I would open the lid it would simply put up a picture of the battery showing how much charge it had. You too??? But have since put it back to booting when lifting the lid.

Don't like some of these changes and would certainly like to have the Mac chime back if possible.

Reply

Answer 2

Feb 19, 2017 9:33 AM in response to Robert Paris

I'm having the same problems. Articles all over the internet talk about the same nvram edit, but it doesn't change a thing here, even when disabling autoboot (which does actually work)

Reply