Deleted posts from Apple’s support forums and active discussions elsewhere online indicate a growing concern for Apple Watch users: the inability to downgrade from a newer version of watchOS to an older version. The issue, which first became apparent when users discovered that watchOS 1.0.1’s heart rate monitoring was less frequent than in watchOS 1.0, is that the Apple Watch apparently lacks a user-accessible recovery or DFU (device firmware update) mode. While there has been a spike in downgrade-related complaints since Apple released the beta version of watchOS 2 on Monday, the issue remains a concern for some watchOS 1.0.1 users, as well.
Without access to such a mode, users with watchOS-related problems are currently being instructed by AppleCare representatives to send their new Apple Watches back to the company for service, often with “out-of-warranty repair” charges. By comparison, iPhone, iPad, iPod, Apple TV and Mac users all have the ability to downgrade to earlier OS versions on their own, without sending their devices back to Apple…
OS upgrades are designed to improve the performance of Apple’s devices, but have occasionally created serious problems for users. Last year, Apple’s release of iOS 8.0.1 infamously broke cellular and TouchID functionality for just-released iPhones, while significant crash bugs in iOS 7 persisted for months across iPads, iPhones, and iPod touches. Apple has rarely pulled buggy OS releases, preferring to address them with subsequent patches, though the cellular flaw in iOS 8.0.1 was quickly deemed severe enough to warrant an exception.
Changes to the Apple Watch, such as reducing the number of heart rate readings in watchOS 1.0.1, are considered improvements by Apple but not by some users, as reader comments demonstrate. Users who bought the Apple Watch for more active monitoring have sought to revert back to watchOS 1.0 to restore the prior functionality. Similarly, some developers whose development Apple Watches are also their personal timepieces have expressed regrets after installing the beta version of watchOS 2, noting that significant battery drain is impacting full-day use of their Watches. While the watchOS 2 beta warns that downgrading is not possible, similar warnings have accompanied iOS beta releases and proved inaccurate thanks to the DFU mode in iOS devices.
The presence of a DFU mode lets users restore their devices to prior, more functional OS versions without involving AppleCare support staff, losing use of their devices, or incurring unnecessary repair fees. After the iOS 8.0.1 cellular problem crippled tens of thousands of devices, Apple instructed affected users to manually downgrade to the earlier 8.0 release while a fixed version 8.0.2 was prepared. A recovery or DFU mode for the Apple Watch would give watchOS users the same do-it-yourself alternative. Since triggering iOS’s DFU mode requires a special sequence of button presses that users would be highly unlikely to discover themselves, it’s possible that the Apple Watch has a similarly hidden feature, just awaiting discovery by a lucky user.
FTC: We use income earning auto affiliate links. More.
Of course they pay for downgrade. I’m pretty sure this is written in the reading box before downloading the beta. But nobody reads that, and cry after because it doesn’t work like they would…
The beta issue was mentioned in the article. End of second to last paragraph. But that doesn’t apply to watchOS 1.0.1.
to be fair, the article shows a picture of the beta and mentions the influx of users wanting to downgrade since the beta came out on Monday, so they kinda bait people into ranting about beta users.
To be really fair, people rant about everything in the comments, and too often haven’t bothered to read properly, even when they’re complaining about other people not reading properly.
Umm what? How can you downgrade in iOS? Apple stops signing certificates for older os. As far as I know it’s impossible to go back to iOS 7. This has been a complaint of iOS users for a while. No surprises here with the watch.
You can downgrade to an iOS version that Apple is still signing. Usually if you install an update on day 1, you can still go back to an older version that same day or even for a few days. WatchOS you cannot do that at all.
ok. makes sense if you do it within that timeframe.
Unfortunately you can’t find out how bad a device might run in a short enough time to downgrade. My iPad was turned into an exercise in frustration after iOS8. It took a little bit to really notice the changes and things happening, then 8.0.1 was SUPPOSED to fix it. By that time it was too late to go back to 7. My only choice was to buy a new one because it became unusable. Now it is relegated to music duty in the garage. Sad but true.
If enough customers complain, Apple will revert the heart rate monitoring method (or at least offer it as an option).
watchOS 2.0 beta already reverted to the original heart rate monitor interval. But of course, the rest of the OS is buggy as hell.
Where’s the documentation for this? I certainly hope 2.0 goes back the original monitoring interval.
“By comparison, iPhone, iPad, iPod, Apple TV and Mac users all have the ability to downgrade to earlier OS versions on their own, without sending their devices back to Apple…”
Factually inaccurate statement for all but the Mac. iPhone, iPad, and iPod touch users are all only able to downgrade to earlier OS versions as long as Apple keeps the SHSH signing window open. Which, for most releases, is a very short period of a few days. Once that window is closed, even if you had run a prior release (say you upgraded from 7.1.x to 8.1.2), you are stuck, just like with the watch.
It gets worse. Apple has created a faustian circumstance: the longer you wait to upgrade–ya know, to get feedback on initial bugs and what not–the more likely you are to get stuck. Further, if you stay on a prior version, say with 7.1.2 on an iPhone 4S for performance reasons, and hit upon a bug that causes issues on your iPhone (with Messages, say, a frequent offender), Apple Support won’t even TALK to you unless you upgrade…and even if you KNOW the current upgrade has OTHER bugs you aren’t willing to endure (say, 8.3 kills Bluetooth in your car). Likewise, Apple Support forces you to upgrade and will make NO ASSURANCES that doing so will FIX your issue; so you upgrade only to find that whatever bug you triggered exists in 8.3 too. Sucker. Now you can’t use Bluetooth in your car AND your Messages are screwed up!
What I find nearly as terrible about this situation is that 9to5Mac is reporting on it as though they’re UNAWARE of this. There have been several calls for Consumer Rights legislation in several states to prohibit this kind of action, however none have succeeded. Maybe because it is beloved Apple that is inflicting this pain, and few others. But that 9to5Mac has remained so wrong on the issue to publish an article this far after the debacles of iOS 6, iOS 7, and iOS 8 rollouts (all bringing considerable bug and regressive performance baggage and not allowing downgrades) rather than using the opportunity to ONCE AGAIN rally the community towards getting Apple to change a terrible anti-consumer policy is disappointing.
As far as software governance goes, their solution has been the best in the market and I, as well as the majority of the developer and security community, will continue to applaud and welcome this push. Forcing general users up the chain and preventing them from falling back down is more of a winner than a loser on pretty much every front.
Sorry, the statement is actually factually accurate. Beyond the short period you cite, there is a multi-month window for beta releases (including public betas, which now exist for both iOS and Mac) in which users can effectively downgrade back to the prior major release or point release. My guess is that you weren’t considering this when you drafted your response, but it’s simply true. So there are windows for downgrading; they’re just not unlimited.
Would it be better to have longer downgrade windows? My answer is a qualified yes — there are valid reasons and arguments on both sides, but I tend to err on the side of greater consumer choice.
It needs to be underscored, however, that the point of the article was quite clearly to address an issue impacting Apple Watch users. Your last paragraph attacks the article because it doesn’t also address problems impacting iOS users (which, by the way, were previously discussed in the linked articles about iOS 7 and 8, as well as many others on this site). It’s going to be very hard for you to rally people to your cause if you attack potential allies as “so wrong on the issue” when they actually agree with you and are working towards the same goal.
I’m in this same boat. As a developer its even worse. I upgraded to watchOS2, iOS9. Now I need to put out an update to an existing app. I can’t run the app from Xcode on my phone because Xcode 6 doesn’t work with iOS 9 and Xcode 7 can’t be used to submit apps to the app store. I can’t downgrade my phone to iOS 8.3 because my watch is at watchOS 2.0 and I won’t be able to use my watch at all.
Apple please tell us the secret formula for reseting the watch. This is not reasonable. I might be able to reset the watch and try to return it to the store. Thats not a great solution for anyone.
Dont install betas on work hardware. Period. Your fault.
your response is unwarranted: as he clearly mentions- he is a developer. Developer’s BETTER be using the latest updates & betas in order to assure THEIR apps work properly!
APPLE should be concentrating on getting THEIR OS’s to work (and when they don’t, Give an avenue to revert backward till a resolution is completed. PERIOD! Apple definitely needs to address these issues- it is in the interest of EVERYBODY.
Really dude, really…REALLY!? He’s a DEVELOPER…man the sheer ignorance sometimes on here…arghsdfjhsdfjlhsdfhs…
Actually, borntofeel is right. Don’t install betas on hardware *that you need for current release support*. I get that for some people it’s not feasible to have 2x Watch, 2x iPhones etc. But then at least be conservative about installing betas and don’t grab b1.
Uhm no. He said he has to do an update for an app that is out now. It’s his fault he didnt keep a phone with iOS8.
He is a developer, so needs to run the bleeding edge occasionally. But he should also know the pitfalls. I have one of every iPhone, a couple iPod Touches, and have several bootable thunderbolt drives. If I needed to do Apple Watch 2.0 development I’d go get a sport edition 38mm…
Apple clearly warned you not to install betas on production hardware you need to work on your apps.
There is no secret to this, simply do not install betas on production hardware.
@triguyfun, BS. Developers are not supposed to install betas on production hardware, that’s always been the case for several years on any platforms. It is well known that installing betas including OS X and Xcode betas will block you from submitting updates for existing apps.
Apple also clearly warns about this with the iPhone, iPad, etc — they say the exact same thing, no downgrade possible — which is actually not even true — you boot to DFU, flash your valid and signed OS, and presto changeo, it’s fixed. Also, if you’re Apple, why put this feature in every other product except the watch? It makes no sense…
Watch is a relatively new platform and it is extremely limited compared to other platforms, of course it is not going to have the same features. Secondly, downgrade isn’t possible once you miss the signing window, that’s why they warned you in the first place.
1) Not all developers can afford two $349/$399 watches.
2) Good luck getting two watches. It took Apple nearly two months to even ship mine.
Let’s get real, here. And there’s no excuse for Apple to be charging “out of warranty” fees when their developer preview borks the device. None.
1. You don’t need to buy two watches, you can still run the watchOS 2 in the simulator, which has been expanded to the point that you don’t need the watch in person to test your apps.
2. What are you talking about, all we’re hearing is that the devs cannot downgrade. That is not the same thing as bricking the device.
Why don’t you just downgrade your phone summit the update and update back to iOS 9?
Have you tried a similar operation on the watch? Press an hold crown and button while attached to a charger, then release button but not crown when the screen goes blank? Maybe?
People complain enough about Apple for stupid stuff so I dont think a website about Apple should talk about stupid people complaining about the fact that a beta is a beta.
IMHO this really doesn’t have anything to do with beta software…it has to do with the fact that the Apple Watch does not have a DFU mode; which means essentially, that if at any time the watch becomes screwed up somehow — and the reasons for that could be numerous, as explained, and IMHO don’t really matter at the end of the day, because– there is no way to fix the issue without sending your watch in to Apple, and _paying_ for it; where as with _every_single_other_ iOS based product, you can fix it yourself simply by booting into DFU mode and restoring to whatever signed and valid firmware is available. I don’t see the point…why would Apple purposely leave out DFU mode on the watch?
“restoring to whatever signed and valid firmware is available.” so you can’t do that without DFU mode on the Apple watch?
“restoring to whatever signed and valid firmware is available.” so you can’t do that without DFU mode on the Apple watch?
Correct; there is no DFU mode available on the Apple watch — for whatever reason, Apple did not put this functionality in with this product, so there is no way to perform a restore. Even the Apple TV’s have a DFU mode…As far as I can tell, you also can not even use the Apple Watch with iTunes on a Mac or a PC _at_all_ — it doesn’t show up under “Devices” in the left hand column.
I suspect that there is a hidden DFU mode that only Apple can access and it’s done through the hidden port, which is probably how they flash them from the factory and “fix” them when people send them in. Pretty stupid IMHO. Guess we’ll hope for this “feature” in Gen. 2 of the Apple Watch lol.
As of right now, there are at least 3 different versions of iOS that Apple is signing for many iOS devices (iOS 8.3, iOS 8.4 beta and iOS 9 beta). So the article is not misleading at all. I just “downgraded” my iPhone 5s today from iOS 9 to iOS 8.3
Wow!! Can you say: BIG APPLE MAJOR FU(%UP!! … This isn’t your Daddy’s TIMEX for sure!
(sales of this product were already questionable, Apple better get their act together Quickly!!)
yes clearly this is going to be the thing that kills Apple Watch.
And that is why I always buy 2nd generation apple products or later…….
This entire discussion has nothing to do with the version of the hardware.
Not sure I understand Apple’s logic on this one…What reason could there be for not putting a DFU mode on the watch? I can’t really think of any reason not to include this…it’s on every other iOS based product.
Jailbreaking.
The watch has already been hacked / JB’d…first by Comex and now by a bunch of other people. Whether or not it has a DFU mode has absolutely *nothing* to do with it…
Could the “hidden port” possibly be a solution to resetting the device? Just curious as to how Apple would repair the device when they receive watches with software issues like this?
That’s what I am thinking –it appears that it’s most likely they use the hidden port to flash and test the watches from the factory, and also to hard flash them when people send them in. They probably have a hidden DFU or JTAG mode that no one can access except for factory software along with the hidden port.
So glad I stocked up on the popcorn earlier today.
As a long time Apple fan, promoter, etc. I’ve learned, wait for Apple Thing II! Never buy the first of anything, unless your a chronicle of history.
Oh yeah, what a big problem… i can see how this affects many hundred people out of millions… Just don’t toy around with your Apple Watch Software and get Apple Care+!
What are you even talking about?
Simple solution: Don’t update as soon an update is available. Unless you’re having serious problems with your device that an update is advertised to fix, why rush to update the same day that it’s available? I didn’t update my Watch OS and I’m glad. I prefer my heart rate be monitored and recorded every ten mins. I haven’t had battery life issues.
What are you talking about? Did you read the article?
Is it even possible to have a DFU mode? Even though you connect your watch to a USB cable, it’s just for charging, right? There’s no data going through the charger, is there?
Apple would have to release a custom cable that connects to the data port on the watch.
Or enable the Bluetooth/Wi-Fi radio so that the Watch could pair with an iPhone or Mac for wireless firmware upgrading.
Not sure why Apple would charge for this. Also if there is a problem with the watch why not get it sent in for repair under your warranty rather than request a Watch OS down grade. That just seems silly and unnecessary. I don’t think downgrading your Watch OS will make it any better. Send it in for warranty repair. If any of the Applecare reps suggest a downgrade then suggest to them I want my watch sent out for repair under warranty, don’t pay them to downgrade your Watch OS.
In my case what I did was:
1) Left the Watch on WatchOS 2
2) Restored iPhone to iOS 8.3
3) Chose a watch face that just tells the time (Chronograph) and put it on Airplane mode.
I won’t have the notifications and a bunch of the smart features for now (either while someone comes up with a way to downgrade or Apple offers an update that will allow the downgrade to 1.0.1) but at least I’ll have a functioning watch, the battery probably won’t run out that quickly (it was running out quicker than 1.0.1 but not as fast as a lot of people mentioned) and I’ll still have the nightstand mode.
It’s a good workaround for now.
While I can sympathize with those trying to go back from 1.0.1 to 1.0, I have no sympathy for “developers” who clearly should realize that DFU mode is for devices that are physically connected via a wire to a computer running iTunes. The watch doesn’t even talk to iTunes and there’s no off the shelf wire to connect it to anything.