Ipod touch 32G 4th generation passcode problem
Started by
garfluver
, Dec 25 2011 10:04 PM
#1
Posted 25 December 2011 - 10:04 PM
#2
Posted 28 December 2011 - 11:17 AM
Hello there,
Try Changing the password for the iPod, then sync with iTunes.
Hope this helps.
Try Changing the password for the iPod, then sync with iTunes.
Hope this helps.
#3
Posted 29 December 2011 - 08:02 AM
We could not reset the passcode as the iPod was disabled.
But, I wanted to let you know that the iPod passcode problem has been fixed incase someone else ever has this problelm.
After calling Apple customer service a few times in the process, we were told to do a restore on the Ipod. We were able to find the directions for this on apple online help. We had already tried to do a restore before calling Apple, but it didn't work due to the fact that we kept stopping the restore process when the following message popped up...
"iTunes could not connect to Ipod because it is locked with a passcode. You must enter your passcode on the iPod before it can be used with i Tunes." During the restore and update (which took a little over an hour)a message popped up saying that "the Ipod could not connect to itunes, enter the passcode". Then a message window pops up saying that you can retry or cancel. (special note** Do not "X" this message off.)
The Ipod showed that it was disabled on the Ipod screen, so we unplugged the Ipod from the computer and tried again several times with the same message showing up. Finally on our last attempt we decided to leave the Ipod attached even though the message still popped up that we couldn't connect to itunes. We noticed that the computer was continuing to download the update so we waited to see what would happen and if it actually would update with the Ipod "disabled". The computer did continue to update the software (after almost an hour). And...after clicking "retry" on the message that originally kept popping up, the restoring process was able to continue!! And the Ipod is now able to be synced to itunes and life is good for my teenage daughter again.
Hope this helps someone else...we spent many hours on this problem and it seems that if we had just let the update continue even though an error window popped up it would have saved us a lot of time and frustration. Am surprised that Apple didn't know this in 3 out of 4 phone calls.
But, I wanted to let you know that the iPod passcode problem has been fixed incase someone else ever has this problelm.
After calling Apple customer service a few times in the process, we were told to do a restore on the Ipod. We were able to find the directions for this on apple online help. We had already tried to do a restore before calling Apple, but it didn't work due to the fact that we kept stopping the restore process when the following message popped up...
"iTunes could not connect to Ipod because it is locked with a passcode. You must enter your passcode on the iPod before it can be used with i Tunes." During the restore and update (which took a little over an hour)a message popped up saying that "the Ipod could not connect to itunes, enter the passcode". Then a message window pops up saying that you can retry or cancel. (special note** Do not "X" this message off.)
The Ipod showed that it was disabled on the Ipod screen, so we unplugged the Ipod from the computer and tried again several times with the same message showing up. Finally on our last attempt we decided to leave the Ipod attached even though the message still popped up that we couldn't connect to itunes. We noticed that the computer was continuing to download the update so we waited to see what would happen and if it actually would update with the Ipod "disabled". The computer did continue to update the software (after almost an hour). And...after clicking "retry" on the message that originally kept popping up, the restoring process was able to continue!! And the Ipod is now able to be synced to itunes and life is good for my teenage daughter again.
Hope this helps someone else...we spent many hours on this problem and it seems that if we had just let the update continue even though an error window popped up it would have saved us a lot of time and frustration. Am surprised that Apple didn't know this in 3 out of 4 phone calls.
#4
Posted 30 December 2011 - 09:58 AM
Good to hear you have solved the issue.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users