I recently received a new iPhone and need to transfer everything, but I can't sign in to my Apple Account. I'm almost certain I know the password, but I've used up my attempts trying different variations. The account recovery process then asked for my phone's passcode, which was also rejected—even though that passcode still unlocks the phone normally. I received a message saying I would get a call or text within a few days to start recovery, but nothing arrived. I restarted the process and now the waiting period has begun again. Is there any way to speed this up or get help in person? Can an Apple Store assist with the recovery, and can I return the new phone if I can't access my account?
3 Answers
Apple Support or an Apple Store can explain the recovery process and confirm that your request is active, but they generally can’t bypass the security waiting period or manually reset the account. Restarting the recovery request usually resets the countdown, so beginning it again likely put you back at day one. It’s best to leave the current request alone and check its status rather than starting over again. Recovery can sometimes complete earlier than the estimated date.
If you still have your old iPhone, iPad, or Mac signed in to the same Apple Account, check whether you can change the password from the device’s account settings. On an iPhone or iPad, look under your name, then Sign-In & Security, and choose Change Password. A trusted device may let you update the password without waiting for account recovery.
The device passcode and Apple Account password are separate credentials, even if you originally chose similar ones. The fact that the passcode unlocks your phone does not guarantee that it will be accepted during account recovery, especially if the recovery system is asking for a different verification step. The store may be able to clarify which credential is being requested, but they can’t override the account’s security checks.
That explains the confusing part: my passcode still unlocks the phone, but the recovery screen rejects it. I may have been assuming it was asking for the same credential when it was actually verifying something different.