iphone7 attempting data recovery

My iPhone 7 had the same issue, twice:

1) Update from 10.0.0 to 10.0.1 by iTunes after restore from an iPhone 6 backup

2) Update from 10.0.1 to 10.0.2 by iTunes but with no backup restore

*Windows 10

The "attempting data recovery" screen took a relatively long time(maybe 10 minutes), and it followed a prompt "press home to recover".

During the process, iTunes was giving a message called "iTunes could not connect to the iPhone because it is locked with a passcode" and did nothing revolves data restore/recovery.

When the update completed, my iPhone seemed to be back to normal.

Although English is not my native language, the words "attempting" and "recovery" bothered me, sounds like there was some "failure" occurred, I searched the web and found nothing, I think maybe this is new from iOS 10.

I will appreciate it if someone can give some information about why this is happening.

Thanks!

--------------------------------------

P.S. There was no any failure appeared on iTunes side except the passcode thing, iTunes status:

Extracting software ->

Backing up iPhone 7 ->

Preparing iPhone for software update ->

verifying updated iPhone software ->

Updating iPhone software ->

verifying updated iPhone software(again)->

Updating iPhone firmware->

iTunes could not connect to the iPhone... , at the same time, "attempting data recovery" happened on iPhone side.

Had this problem when I did the first update to 10.0.2 (can't remember if it started on 10.0.0 or 10.0.1)
It failed to recover, TWICE, so I put it into DFU mode and restored it that way. This happened again from 10.0.2 to 10.0.3......thankfully the recover worked..... I had another problem with my phone, where the speaker was almost certainly blown, or otherwise faulty, so I took it to an apple store, they replaced the phone (after a long process we won't go into here) I got the new phone needing an update (didn't check what version it was on, shame on me) using my same win 10 pro pc (on the same day i did the 10.0.3 update on the first one) it had 0 problems updating to the new IOS. I can draw one of two possible conclusions from this, 1) the individual phones we are having trouble with are the problem, 2) the fact that I set it up "as new" could mean that my "restore from backup" from my iphone 6+ was the issue in some way. If the issue persists into the next ios (hopefully 10.1 with portrait mode) we may all get to test this. Of course they may have figured out the problem by then as well.

I've had exactly the same issue as everyone else when updating through iTunes (Windows 10, anniversary update). This has happened on both the update to 10.0.3 and 10.1.

I contacted Apple Support this morning but they claimed they weren't aware of the problem. The advised solution was to wipe the phone and restore from backup, as it might have been a glitch on the software provided with the phone. They also said just running updates would not remove this glitch and I'd have to start from scratch.

All seems a bit weird to me - I've never had this problem before and I didn't like the word 'attempting'...

If your iPhone, iPad, or iPod touch won't turn on - Apple Support
Take care!

I had the same issue. I restored my iPhone 6S backup to my new iPhone 7. iTunes then asked to update to 10.0.1. After rebooting, the phone appeared to fail the validation step and then went into "attempting data recovery". After completing, the phone appears to work fine, and reports 10.0.1 installed.

So I have an iPhone 7 128GB & when I got the phone I updated from 10.0.0 to 10.0.1, using iTunes on Windows 10, before restoring from a backup. On the final boot up I got a screen saying "Attempting data recovery"

When 10.0.2 released, I did the same thing. iTunes update on Windows 10. Update completes, final reboot & again "attempting data recovery"

My roommate has an iPhone 7 Plus 128GB. Going from 10.0.0 to 10.0.1 via iTunes on their Windows 10 machine (but a different computer) did the same thing (though they restored from backup first). They then updated over-the-air to 10.0.2 but did NOT see the "attempting data recovery" screen. So 10.0.0 to 10.0.1 via iTunes = "attempting data recovery", 10.0.2 via OTA = no "A.D.R" screen.

I did call Apple, but they say this was how the new iOS does it now. So I pulled my iPhone 6 out (as I'm still waiting to send it to AT&T) & did the update from 10.0.1 to 10.0.2. I did not get the "Attempting Data Recovery" screen at all. So it can't be the iOS version.

I called Apple a 2nd time & they said they would flag it, but that I shouldn't worry. Personally I don't think this is normal behavior.

I had a call back from a Senior Apple Tech yesterday who advised to update to the lastest iTunes and restore my phone from new with 10.1.1 to see what happens. In the process of downloading iTunes 12.5.3 and ios 10.1.1 as we speak (as I type).

Hi

Because its a new iPhone i would return to place or purchase

If its apple store make an appointment .

Cheers

Brian

My iPhone 7 was freezing on the homescreen after logging in with touch iD. The screen did not respond. Tried to restart the phone, but it didn't reboot the normal way. Kept getting the black screen with the Apple logo, for 10 minutes. Tried it over an over, but no result. When I put the iPhone into DFU mode it updated the phone to 10.0.3 with the similar 'attempting data recovery' at the end of the update. After this my phone seems to work fine again.

Anyone else who had the same problem with a freezing homescreen or the endless reboot?

I have this issue on all 3 of my iPhone 7's so I don't think it is just an issue of a bad backup or restore. Also people have setup as new device and this doesn't fix the issue. I just think everyone will need to submit an email support ticket to start to raise the issue. I think a majority are doing an OTA update and not encountering this issue.

Same happened to me from 10.0.1 to 10.0.2 it restarted with the comment "attempting data recovery". Good I had made a backup before the update, but after recovery everything went fine and 10.0.2 appeared.

Attempting Data Recovery... With Video!

The history:

1. Updated my iPhone 7 128GB from 10.0.0 to 10.0.1 on launch day in the USA. This is a clean update with the phone setup as new. Upon reboot after install I saw "Press Home to Recover". Once I pressed home I got the "Attempting Data Recovery" Screen.
2. Roommate on iPhone 7+ 128GB updates via iTunes (different computer than the iPhone 7) 10.0.0 to 10.0.1 after a restore of their backup. Upon reboot after install "Press Home to Recover" followed by the "Attempting Data Recovery" screen.
3. Update my iPhone 7 128GB via iTunes from 10.0.1 to 10.0.2. Upon reboot get the "Press Home to Recover" followed by the "Attempting Data Recovery" screen.
4. Roommate updates iPhone 7+ 128GB via Over-the-Air option from 10.0.1 to 10.0.2. Upgrade completes & home screen returns without a "press home to recover" & "attempting data recovery" did not show up.
5. Update my iPhone 7 128GB via iTunes from 10.0.2 to 10.0.3. Upon reboot get the "Press Home to Recover" followed by the "Attempting Data Recovery" screen.
6. Roommate updates iPhone 7+ 128GB via Over-the-Air option from 10.0.2 to 10.0.3. Upgrade completes & home screen returns without a "press home to recover" & "attempting data recovery" did not show up.

Here's a link to the sped up video. It took just over 12 minutes to update the phone due to this "Attempting Data Recovery". I sped up the video to 2x to get it to just over 6 minutes: https://youtu.be/O4rtZ5NQYMI

All updating via iTunes was done on a Windows 10, x64 fully up to date machine with the latest versions of iTunes.

So Apple, any ideas?

Ok, so I had the problem again, going from 10.0.3 to 10.1. This time my phone WAS "restored from backup", which I did after the last update. Not enough to be conclusive, but I will take this to mean it is likely an "iphone 7/7+ which is not set up as new"...problem

What I can say for certain, to 10.0.2 (from 10.0.0 or 10.0.1 idk) i had this problem (was "restored" from my iphone 6+) ...failed to recover, twice, eventualy DFU to fix

from 10.0.2 to 10.0.3 had this problem (at least THIS time it did "recover")

from 10.0.x to 10.0.3 (new phone after speaker problem) which had not been "restored from backup, was a-ok no issues

from 10.0.3 to 10.1 on that new phone (which NOW has been restored from my iphone 7+ backup (and by extension....the iphone 6+ backup)) is...right now as I type this, ATTEMPTING to recover...and is now about halfway done, will update with any news if I find any, apple, plz, fix
edit1, to all of this, it is from fully updated windows 10 Pro PC

edit2, succesful recovery, had to re-enter passcode (25digits) (after the twice you do it to "recover") and my apple password, was asked to upgrade security (2 factor authentication for itunes stuff) chose NOT to...if i lose my phone i want to be able to FIND it, withotu HAVING a text sent to it saying so....which gives me a code i won't get, cause i DONT have the phone...
this time with recovery, my credit card in apple pay was not deleted, and by all accounts, all of my accounts are still signed in. (facebook, google/youtube, outlook, etc...)

portrait (in beta) is now an option in camera.

I've had a new Iphone 7 Plus for a month now. There have been 3 incremental upgrades to IOS 10 since I've received my new phone. I had the same "attempting data recovery" situation the first 2 times. I contacted Apple support and they suggested I make an appointment and perform the next upgrade at the Genuis Bar" at the Apple store in order for them to see what was going on. So today I did that and the 10.1.1 ensuing 10.1.1 update produced the same result, "attempting data recovery". At that point the technician went for help (level 2?). This guy then says "oh that's the new message for Iphone 7" . Clearly my guy didn't know that, so I'm suspicious. The upgrade worked and as far as I can tell all data has been restored. "Attempting data recovery" is clearly a disturbing message!

I only encountered this when updating via iTunes. No such problem when updating directly via wifi. Also, though it took 15-30 minutes, the data tecovery did work.