We were all stoked for Apple's new iPhone update for iOS 10. It promised new game-changing features in iMessage and much more.
Unfortunately, some who updated their phones weren't able to check out the new features at all.
If anyone tries to call me, sorry I have a brick phone now #IOS10 #applefail pic.twitter.com/rssRrEKgxp — Christypher (@ViaChristy) September 13, 2016
Within the first hour of the update's release, iPhones totally "bricked." The update made phones unusable and restoration was necessary.
Of course, this information exploded on Twitter. Lots of people waited it out, fearing for their lives phone.
A spokesperson for Apple shed some light on the issue to Daily Mail,
We experienced a brief issue with the software update process, affecting a small number of users during the first hour of availability. The problem was quickly resolved and we apologize to those customers. Anyone who was affected should connect to iTunes to complete the update or contact AppleCare for help.
Apple provided instructions on how to un-brick iPhones, just in case it happens to anyone else (even though it shouldn't now).
The instructions break down how to restore your iPhone through iTunes by using recovery mode. You'll definitely need the latest version of iTunes, so make sure your computer is up to date as well.
You'll have to connect your device to a computer and restart it by holding the sleep button and the home button for at least ten seconds. Hold them until recovery mode shows up on the screen.
iTunes should then prompt you to "restore" or "update" your phone. Select update.
If after 15 minutes you're still seeing recovery mode on the screen, you'll have to repeat these steps and select "restore" instead of "update."
All you have to do after that is set up your phone as you normally would if you were just taking it out of a new box.
The full instructions can be found here.
Luckily, Apple jumped on the problem early and if you update it now, you should be good.
But still, I'm sure someone over there got fired yesterday. Oops.