The phone was made weeks ago in China. How might someone suggest the latest OS be installed on a phone without releasing iOS, installing it to the phones, then beginning the distribution of the phone? That's illogical.
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.
Warning: Update Your iPhone 15 to iOS 17.0.2 Before Transferring Data From Another iPhone
- Thread starter MacRumors
- Start date
- Sort by reaction score
The phone was made weeks ago in China. How might someone suggest the latest OS be installed on a phone without releasing iOS, installing it to the phones, then beginning the distribution of the phone? That's illogical.
Think Apple are on this now. Just setting up my new phone, and as soon as it connected to WiFi and activated the phone a warning came up that you MUST update the software if you want to copy from another phone.
The advantage is you dont have to have all your data stored in iCloud.
I remember we were promised no significant new features due to iOS 17 being the stability update !!!!
Transfer failure happened to me without updating to newest iOS version. I wish I had known or read this article. After the update installed, transfer ran smoothly.
When I was at the Apple Store this morning, they were having everyone restore from iCloud. They said it was faster.
Better to be on 17.0.1 because then the device will definitely prompt you to update to 17.0.2 before transfer.
I had an issue setting mine up this morning where my 15 had already taken the cell service from my 13, and after the 15 rebooted it went back to the start of its “transfer from another phone” process. However it no longer would see my 13…
If you are unboxing an iPhone 15, iPhone 15 Plus, iPhone 15 Pro, or iPhone 15 Pro Max today, make sure to update the device to iOS 17.0.2 before transferring data to the device from another iPhone, or else you might encounter issues.
iOS 17.0.2 is only available for the iPhone 15 lineup. Apple says the update fixes an issue that may prevent transferring data directly from another iPhone during the device setup process, so installing it is very important. The update should appear during the setup process, or it can be installed via the Settings app under General → Software Update if you proceeded to set up the device as new and transfer data later.
If you already attempted to transfer data from another iPhone before updating to iOS 17.0.2, and your iPhone 15 is now stuck showing an Apple logo, Apple has shared a new support document with steps on how to restore the iPhone:After restoring the iPhone 15 and updating it to iOS 17.0.2, the process of transferring data from another iPhone can be restarted.
Article Link: Warning: Update Your iPhone 15 to iOS 17.0.2 Before Transferring Data From Another iPhone
So I took the 15, set it up without transferring from my 13, reset the 15 to factory settings, elected to keep my eSIM on the 15 (part of the reset process), and started the onboarding all over again. Worked like a charm that time.
Someone needs to talk about the whole iPhone rebooting while updating thing, that’s where I think things went wrong with me because I had already paired the two phones before the update.
Of course, after you spend $1500, they do not want to spend more than 5 minutes with you.
We do not have Apple Store within 3 hours. Just Best Buy so bought online and waiting its arrival. I cannot backup to iCloud my Comcast WiFi is not best but no other options in neighborhood (200 mbs down, 10 mps up) I tried to use the free icloud backup but was going to 8 plus hours and barely getting to 1/5 done. We do not have higher speed available and cell is weak near house so Wifi is it.
will have to use the backup to macbook I made today then
I'm having some issues updating to 17.0.2, anyone else run into this or know a fix? Iv'e tried twice already.
Is there any difference in terms of what is brought over by doing a device-to-device transfer versus making an encrypted backup on a Mac and restoring from that? Is one more thorough than the other or are they identical in terms of bringing over sensitive information and passwords?
Mine never stalled. It took about 2 minutes and everything was fine. I set up as new and just downloaded stuff from iCloud. Even transferring my eSIM from my 14PM was seamless.
Setting up as new appears to be a way to avoid the error. Transferring data from another phone requires the update. Transferring eSIM however appears to not requiring the update and was seamless. That was what I experienced today. I prefer to restore from backup and transfer data because I do not have to reinstall all my apps that I have on my previous phone. I just do not have the courage to do that
Wow… these comments. It sincerely makes me wonder if this forum is hosting a considerable quantity of PR firm sock puppets. It is so hard to believe that some people could lose their **** so extensively over occasional hiccups, with many of them looking to be commenting on the article rather than experiencing the headaches.
The logistics of launching a new iPhone, all the server-side data transfer and communication going on condensed into a tight timeframe, the fact that it is all happening at once with limited staff for such an event (lol at the person above commenting on staff time limitations without a moment of thought), and that the process includes activation and communication with other carries on top of Apple’s own systems, as well as dependence on aspects of a user’s home network, make this a pretty staggering feat to handle from an IT perspective. It usually doesn’t go without some headaches, but the progress has improved year-to-year, and nobody else is doing anything comparable. I would love my phone upgrade to be free of all headaches, but something like a known issue with one manner of activation that is handled by an in-activation prompt to upgrade is not exactly causing me to lose sleep.
My headache at the moment seems to be related with AT&T activation. Came here to see if I could find any hints on that while I am installing this new update.
The logistics of launching a new iPhone, all the server-side data transfer and communication going on condensed into a tight timeframe, the fact that it is all happening at once with limited staff for such an event (lol at the person above commenting on staff time limitations without a moment of thought), and that the process includes activation and communication with other carries on top of Apple’s own systems, as well as dependence on aspects of a user’s home network, make this a pretty staggering feat to handle from an IT perspective. It usually doesn’t go without some headaches, but the progress has improved year-to-year, and nobody else is doing anything comparable. I would love my phone upgrade to be free of all headaches, but something like a known issue with one manner of activation that is handled by an in-activation prompt to upgrade is not exactly causing me to lose sleep.
My headache at the moment seems to be related with AT&T activation. Came here to see if I could find any hints on that while I am installing this new update.
I don't know why that would surprise anyone? Same procedure as last year? Same procedure as EVERY year ...
https://forums.macrumors.com/thread...s-12-things-to-do-first.2403091/post-32505675
I have all the time this weekend. This is my long weekend (only get them once a month) and was stoked that it fell on Apple iPhone launch day, and the weekend that a hurricane is coming in my area.Setting up as new appears to be a way to avoid the error. Transferring data from another phone requires the update. Transferring eSIM however appears to not requiring the update and was seamless. That was what I experienced today. I prefer to restore from backup and transfer data because I do not have to reinstall all my apps that I have on my previous phone. I just do not have the courage to do that
That's cool you worked so closely with Scott Forstall to know he only made one mistake. Also, it seems to have had more to do with him being unapologetic. Everybody makes mistakes, some huge. What matters is how you handle them and from the information that was available at the time, it seems Forstall handled it poorly.