Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

karinatwork

macrumors 6502
Original poster
Mar 2, 2009
293
325
British Columbia, Canada
...have you updated to 5.1.1 yet? I'm still on the fence. Too much stress was caused by this ordeal. Got a replacement from Apple, but I'm too scared to even update to 5.0.1.
 
...have you updated to 5.1.1 yet? I'm still on the fence. Too much stress was caused by this ordeal. Got a replacement from Apple, but I'm too scared to even update to 5.0.1.

Hello from a fellow BC member. I updated to 5.1.1 without a snag. There's another thread on here where people report their success. I think 5.1.1 is turning out to be a safe update. 5.1 was an anomaly.
 
...have you updated to 5.1.1 yet? I'm still on the fence. Too much stress was caused by this ordeal. Got a replacement from Apple, but I'm too scared to even update to 5.0.1.
Updated to 5.1.1 on my repaired , brick watch. No issues.
 
I didn't get bricked, thanks to those who reported the issue here. I did however update 2 watches successfully to 5.1.1. No issues at all.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.