Apple's WatchOS 5.1 update is bricking some Apple Watch devices

Apple's WatchOS 5.1 update is bricking some Apple Watch devices

Straight after its Brooklyn event earlier today, Apple began rolling the WatchOS 5.1 update to its range of Apple Watches. The software activates the ECG feature on Series 4 models in the US and also introduces support for 70 new emojis and Group FaceTime but, from the looks of things, not everyone is having luck with the new software.

As spotted by 9To5Mac, a number of users across both Reddit and Twitter have begun reporting issues with the update. More specifically, it appears the latest WatchOS version is bricking certain Apple Watch models, causing them to remain permanently stuck on the Apple logo. And, rather unfortunately for users, it appears there is currently no fix. This is despite multiple attempts from owners that have involved restarting both the affected wearable and paired iPhone, and also unpairing the devices.

Apple is yet to pull the new WatchOS 5.1 update so it's unclear at this point how many users are affected by the issue. However, those of you who are will likely need to contact Apple Support and request a replacement device. Furthermore, users who are yet to update may want to hold off on the new software version until Apple corrects the problem.



1. gamehead unregistered

You were on a roll Apple.

2. darkkjedii

Posts: 31369; Member since: Feb 05, 2011

Didn’t brick mine, sorry to those who’re affected.

5. strategic_developer

Posts: 1627; Member since: Jul 17, 2018

It was. Rokw when you bought it /s. I jsut ordered a series 4 today since VZW is offering me a nice deal to get one.

3. lyndon420

Posts: 6840; Member since: Jul 11, 2012

Hahahaha....oops - it slipped out!! But seriously...this is why it's a good idea to hold off on updating our devices. Every single app of mine (including an OS upgrade to Google's latest / and worst) screaming for an update on the Play Store, but I refuse to update them as they are working perfectly fine the way they are. If an app demands an update to prevent it from working due to lack of old software support, then I'll consider the update. But if it ain't broke....I ain't fixing it.

6. strategic_developer

Posts: 1627; Member since: Jul 17, 2018

You shouldn't have to be s armed to update. I've never had a Samsung brick or start working funny because of an update that I am aware of. So much the better quality control factor. And yes bad updates can happen. But kn Andeoid they are rare due to more hands doing the through testing. Apple obvious doesnt throughly test updates. They are all the same watches. How did this not happen during testing? It they just dont care.

4. cheetah2k

Posts: 2275; Member since: Jan 16, 2011

And people bag out Samsung devices.... Ah well... RIP

7. CableTelcontar

Posts: 95; Member since: Nov 19, 2014

Ever wonder why non vanilla android devices take forever to get updates? If Apple updating only 1 OS to a discrete set of devices that they made and control have these issues, imagine what the myriad android OEMs have to go through to update their massive catalogue of devices

8. strategic_developer

Posts: 1627; Member since: Jul 17, 2018

Apple does see many problems inhouse. They just dont care. They now have that, we can fix it later mentality

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit for samples and additional information.