Can't update watchOS 2.0 (13S343) to 2.1

Really weird...

Try to Hard reset your Apple Watch by pressing and holding the side button and the Digital Crown for about 10 seconds.

Hi Constantine,

Yes, I happen to have the exact same issue and also haven't been able to solve it yet. Some of the things I've tried thus far are:

• Restarting the iPhone and watch, in both orders
• Hard resetting the iPhone and watch
• Resetting the network settings
• Manually deleting the update file from the watch
• Wiping the watch
• Un- and re-pairing the watch
• Pairing the watch with a different iPhone
• Downloading the update via a different network

Unfortunately, all to no avail. I did have a chat with someone from Apple Support about this issue, but we weren't able to figure out what the problem is. The suggestion was to contact support via telephone, but I haven't yet gotten around to doing so.

Cheers,

Erik

Hi Erik,

Wow, this is dissapointment. I hope this can be fixed with new watchOS release..

Thanks,

Constantine

I've tried it, no result.

How were you able to "Manually deleting the update file from the watch"? I didn't think we had access to the watch file system directly?

I believe Erik refers to Configuration Profile that should be installed on iPhone and watch prior to install beta.

That makes more sense. I thought maybe he was referring to the Watch OS 2.1 file, which seems to be transferred from the iphone watch app, but I don't think we have access too.

There is a possibility you are seeing a regional problem with the Apple Update. Maybe Apple support can identify that, but if not, then it usually resolves itself after a few days. Do you both happen to be in a similar geographic location? My update ran cleanly for Watch OS 2.1 (Philadelphia, PA, USA region), but it makes me wonder if maybe that is the problem. Either that or a local networking issue, or a true hardware issue on the watches.

I was refering to (what I presume to be) the OS update. In the iPhone's watch app under General > Usage it lists 'Software Update' (301 MB) which can be deleted. Once you do, the update will be re-downloaded on the next update attempt. However, it keeps downloading the 2.0 update.

Yeah, guys in chat support told me that. No result.

I've talked to support over the phone and they adviced me to request technical support https://developer.apple.com/support/technical/

We'll see. Hopefully it's not hardware issue.

For completeness sake, this is what's printed to the console when trying to install the update:

Dec 13 00:08:10 iPhone subridged[988] <Error>: __main_block_invoke92: Install error Error Domain=SUBError Code=12 "Failed to apply update" UserInfo={NSLocalizedDescription=Failed to apply update, NSUnderlyingError=0x157e1fa20 {Error Domain=MobileSoftwareUpdateErrorDomain Code=2 "Could not personalize boot/firmware bundle." UserInfo={NSUnderlyingError=0x157e32370 {Error Domain=PersonalizationErrorDomain Code=3194 "AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build." UserInfo={NSLocalizedDescription=AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build.}}, NSLocalizedDescription=Could not personalize boot/firmware bundle., target_update=13S344}}} with userInfo {
     NSLocalizedDescription = "Failed to apply update";
     NSUnderlyingError = "Error Domain=MobileSoftwareUpdateErrorDomain Code=2 \"Could not personalize boot/firmware bundle.\" UserInfo={NSUnderlyingError=0x157e32370 {Error Domain=PersonalizationErrorDomain Code=3194 \"AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build.\" UserInfo={NSLocalizedDescription=AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build.}}, NSLocalizedDescription=Could not personalize boot/firmware bundle., target_update=13S344}";
  }
Dec 13 00:08:10 iPhone Bridge[987] <Warning>: -[COSSoftwareUpdateController _manager:didFailInstallation:withError:] - _suState: (Installing); update: (
             HumanReadableUpdateName: watchOS 2
             ProductVersion: 2.0
             ProductBuildVersion: 13S344
             ProductSystemName: iOS
             Publisher: Apple Inc.
             DownloadSize: 13036696
             PreparationSize: 315830122
             InstallationSize: 0
             TotalRequiredFreeSpace: 315830122
             DocumentationID: watchOS2GM
             MarketingVersion: (null)
             CurrentDenialReasons: (null)); error: (Error Domain=SUBError Code=12 "Failed to apply update" UserInfo={NSLocalizedDescription=Failed to apply update, NSUnderlyingError=0x15811d7a0 {Error Domain=MobileSoftwareUpdateErrorDomain Code=2 "Could not personalize boot/firmware bundle." UserInfo={NSUnderlyingError=0x15813c190 {Error Domain=PersonalizationErrorDomain Code=3194 "AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build." UserInfo={NSLocalizedDescription=AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build.}}, NSLocalizedDescription=Could not personalize boot/firmware bundle., target_update=13S344}}})

I am seeing the same behavior with my AWS on 343 and iPhone 6 on 9.2. I wonder if Apple stopped signing the 344 update and we need that to move forward?

Worth noting that I did not see that behavior on my other AW when updating from 344 (kept this one up to date)

I am also seeing the same logs!:

Dec 17 07:59:01 iPhone subridged[1648] <Error>: __main_block_invoke92: Install error Error Domain=SUBError Code=12 "Failed to apply update" UserInfo={NSLocalizedDescription=Failed to apply update, NSUnderlyingError=0x15cd177e0 {Error Domain=MobileSoftwareUpdateErrorDomain Code=2 "Could not personalize boot/firmware bundle." UserInfo={NSUnderlyingError=0x15cd2c1c0 {Error Domain=PersonalizationErrorDomain Code=3194 "AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build." UserInfo={NSLocalizedDescription=AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build.}}, NSLocalizedDescription=Could not personalize boot/firmware bundle., target_update=13S344}}} with userInfo {
      NSLocalizedDescription = "Failed to apply update";
      NSUnderlyingError = "Error Domain=MobileSoftwareUpdateErrorDomain Code=2 \"Could not personalize boot/firmware bundle.\" UserInfo={NSUnderlyingError=0x15cd2c1c0 {Error Domain=PersonalizationErrorDomain Code=3194 \"AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build.\" UserInfo={NSLocalizedDescription=AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build.}}, NSLocalizedDescription=Could not personalize boot/firmware bundle., target_update=13S344}";
  }
Dec 17 07:59:01 iPhone Bridge[1646] <Warning>: -[COSSoftwareUpdateController _manager:didFailInstallation:withError:] - _suState: (Installing); update: (
              HumanReadableUpdateName: watchOS 2
              ProductVersion: 2.0
              ProductBuildVersion: 13S344
              ProductSystemName: iOS
              Publisher: Apple Inc.
              DownloadSize: 13036696
              PreparationSize: 315830122
              InstallationSize: 0
              TotalRequiredFreeSpace: 315830122
              DocumentationID: watchOS2GM
              MarketingVersion: (null)
              CurrentDenialReasons: (null)); error: (Error Domain=SUBError Code=12 "Failed to apply update" UserInfo={NSLocalizedDescription=Failed to apply update, NSUnderlyingError=0x1566c14e0 {Error Domain=MobileSoftwareUpdateErrorDomain Code=2 "Could not personalize boot/firmware bundle." UserInfo={NSUnderlyingError=0x15677d610 {Error Domain=PersonalizationErrorDomain Code=3194 "AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build." UserInfo={NSLocalizedDescription=AMAuthInstallBundlePersonalize() failed: This device isn't eligible for the requested build.}}, NSLocalizedDescription=Could not personalize boot/firmware bundle., target_update=13S344}}})

I called Apple Support and spoke to 3 senior advisors who forwarded my request to engineering a few days ago. Engineering responding asking for logs so I just replied with this. They refused to send a replacement since they are unsure if this is a hardware issue. What a nightmare!

Edit: Have a Genius bar appointment setup for Saturday to see if I can get a replacement.

I just got off the phone with an Apple advisor as well. It seems the official solution at the moment is to physically take your device to a service point. Apparently, they maybe able to update the watch. Because this poses somewhat of a logistical problem for me, the advisor has agreed to first forward my email to engineering, before taking that route. I've also included a logfile and a link to this thread.

I am stuck at the same point, have an appointment for this Saturday. Although I really don't want to waste more time on this issue! I have also submitted a Technical Support request through the Dev center to see if I can get any other helpful response/solution/replacement