No. If you want to reinstall 10.2.1B2, you can restore to 10.2, set up as new, install the profile, then restore your backup from 10.2.1.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
IOS 10.2.1 Beta 2 Changes, Bug Fixes and More
- Thread starter atlchamp
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
No. If you want to reinstall 10.2.1B2, you can restore to 10.2, set up as new, install the profile, then restore your backup from 10.2.1.
Also, anytime you're backing up due to participation in the beta, its best to do an encrypted backup. That way you will preserve any health data on your phone if you have to restore.
Its been almost 3 weeks now? Why not just stick it out 4 more days. 10.2.1 should be released shortly. If not 10.3 could be out Tuesday for beta testing. Then you don't risk losing data. Food for thought.
On second thought, you could use the option+update method in iTunes to revert to 10.2 without losing data. Sometimes the phone acts up a little, but it eventually settles down.
True. That makes sense. Is the option+update able to be done in a win 10 machine?
Last edited:
Is that new? I thought you had to do the encrypted backup to do that? That'll save me a lot of trouble in the future if so!
Nope, ever since the health app launched in iOS 8, iCloud backup has saved health data. I believe it was announced in the original keynote, or the support articles that came out immediately following. It wasn't until iOS 10 that you saw the health toggle in iCloud backup, but it had previously always automatically been backed up. I restored my launch day iPhone 6s from an iPhone 6 iOS 8 iCloud backup and my health data was there.
I still prefer encrypted because iCloud backups take forever, but I keep iCloud backup on as a fall back. iCloud backup is pretty much identical to an iTunes encrypted.
[doublepost=1483633092][/doublepost]
Whats the problem?
It used to be that editing the info.plist file and changing the version and build # would allow to use a newer backup on older version iOS. NOT SUPPORTED METHOD. but it has worked fine in the past. Not tried with iOS 10 tho. Also a reset all settings is recommended afterwards to get things back normal to the older version you are restoring to.
Typically if you do this a "reset all settings" afterwards will resolve things. Since the settings could be different between versions but in this case most likely no difference.
Is that the problem? My AirPods have been cutting out audio. I have the 7+ with Intel modem.
Yup, just hold shift and click update then select the update file to install
As soon as the connection to my car stereo, or any other Bluetooth device happens, my music gets garbled up and I've since noticed that if I am running navigation or any other apps in the background, as there is activity (like an email coming through) The music gets distorted badly.... Its horrible.
Anyone else noticing that Bluetooth keeps cutting in and out or turning on and off. I think this happened awhile back too. I'll look at my watch and see the disconnected icon or be looking at the phone and notice the Bluetooth icon disappear, come back as grey and flicker and then turn on as normal. Seems to only happen with the watch, nothing else. Maybe it's a watchOS 3.1.3 beta issue.
Same happens for me when using android Wear Watch and Powerbeats 3 at the same time.
I have the same problem with Bluetooth keeps cutting. Received my new AirPods yesterday and they dropps their connection with my iPhone.
7+ and I've never really had too much of a studder problem in the first place.
I'm still on 10.1.1, seems like this beta is a mess overall? Battery issues, bluetooth issues, itunes issues...wth is apple doing? Along with all those Tmobile users have issues with 10.2 and LTE, this seems like the worst update apple's given out for a while.
Nope 10.2.1 is quite stable here. No battery issues, no BT issues, nothing with iTunes (only backup with itunes tho). I use Verizon and no issues and have not seen any reports from ATT users so apparently t-mobile issues is with T-mobile (maybe a carrier file) not iOS.