I think maybe the OP did not wait for the update to finish. Mine rebooted and had a blank screen for well over a minute before rebooting again. Mine did not power off, when done it booted up by itself!
Well if you're right, you still can't completely blame the OP. If it looks like a crash, it's entirely reasonable that one would treat it like a crash. If firmware is being modified and force shutdown may cause major problems when updating, Apple should have made that clear to the user before the update starts.I think maybe the OP did not wait for the update to finish. Mine rebooted and had a blank screen for well over a minute before rebooting again. Mine did not power off, when done it booted up by itself!
Well if you're right, you still can't completely blame the OP. If it looks like a crash, it's entirely reasonable that one would treat it like a crash. If firmware is being modified and force shutdown may cause major problems when updating, Apple should have made that clear to the user before the update starts.
Fair enough, however a botched normal software update does not cause a machine to be bricked, and software updates (apart from this one obviously) do not cause the screen to go black for over a minute. So again, blaming the OP for bricking their computer because they thought it had crashed is unreasonable.Sorry but the instructions for the update, if read by the OP, clearly states that your screen will go blank for a minute or longer. My 2018 MBPro 15 looked like it was turned off for well over a minute until it rebooted into the Apple OS.
It was my understanding that there was zero mention of the update modifying firmware. Apple have always clearly outlined which updates are for firmware. Also, my memory of previous firmware updates was they show a progress bar.For the OP to state that his just turned off, tell me he did not wait for the firmware to finish updating. That was a critical error during a firmware update.
Fair enough, however a botched normal software update does not cause a machine to be bricked, and software updates (apart from this one obviously) do not cause the screen to go black for over a minute. So again, blaming the OP for bricking their computer because they thought it had crashed is unreasonable.
It was my understanding that there was zero mention of the update modifying firmware. Apple have always clearly outlined which updates are for firmware. Also, my memory of previous firmware updates was they show a progress bar.
The main point is that this is not completely the OP's fault, so people should stop blaming them, and offer some constructive advice.
Although I must admit the OP's click-bait thread title, and not explicitly asking for the help they obviously need, doesn't encourage positive community sentiment. But neither does Apple's obviously rushed solution to a throttling problem which should have been identified and internally fixed months ago.
100% agree, but did Apple's description of the software update mention a firmware modification?If you're flashing firmware and it is interrupted the firmware will be unusable. The computer cannot boot without viable firmware. You'd need a 2nd backup firmware to switch to, but that would complicate things and cost more money. Also you wouldn't ever want to create a system that could leave some users running computers permanently switched to the unflashable protected backup firmware that has critical bugs in it that leaves the computer vulnerable to malware. So there's that to consider as well.
Best to consider firmware flashings something that must not be interrupted under any circumstance, ever. One advantage of being a laptop over a desktop computer is the built-in battery, so power loss is much less likely to be a cause of failed firmware flashings... 🙂
I agree that others have offered thoughts on what the problem is. I disagree that others have offered solutions.
Saying "you did this wrong, I did it right and it worked fine for me" isn't helpful when your computer doesn't work.
oh, thanks for all the responses. already spoke to an apple rep about the issue and did the reset erasmus suggested with them and nothing worked.
as some suggested that i might have interrupted the firmware update and i can tell you that i didnt, i left the laptop open on the blank black screen for well over 30 mins before attempting to check if it was still working... i was busy playing with my 13" MBP at that time and didnt even bother to check on it
i have a genius bar appointment on saturday but at this point, i like the 13" and maybe just return this as it was literally just taken out of the box. i am curious as to what the problem was though...
If I were you I would just return it.
Personally, if it were me, I'd not look to diagnose it, and just return it.dont you guys want me to report what the issue is?
Personally, if it were me, I'd not look to diagnose it, and just return it.
Why? Are you more interested in spending time messing with a defective machine, when in the end, you'll be better off getting it replaced?meh you guys are no fun...
Why? Are you more interested in spending time messing with a defective machine, when in the end, you'll be better off getting it replaced?
No, I like helping people as best as I can, and I like discussing apple products 🙂because we like hearing about problems here, no?
No, I like helping people as best as I can, and I like discussing apple products 🙂
What do you think?is this normal?
This thread took an odd turn.What do you think?
I already offered my advice in that you should return it, but I don't think you're interested in that solution ¯\_(ツ)_/¯
What do you think?
I already offered my advice in that you should return it, but I don't think you're interested in that solution ¯\_(ツ)_/¯