iOS 7 forgot restrictions passcode

Damienmex

based on the error message you described above, my best guess is that you didn't copy/paste the info as I mentioned.

I made the highlighted changes below:

<key>SBParentalControlsBlockTimeIntervalSinceReferenceDate</key>

<real>362258969.244102</real>

<key>SBParentalControlsEnabled</key>

<false/>

<key>SBParentalControlsFailedAttempts</key>

<integer>0</integer>

<key>SBParentalControlsMCContentRestrictions</key>

<dict>

<key>countryCode</key>

<string>us</string>

</dict>

<key>SBParentalControlsPIN</key>

<string>1234</string>

make sure you you add SBParentalControlsPIN under /dict as shown above and set SBParentalControlsEnabled to false. Review what's is written above and try again. That worked for me and for other people as well.

Hope this helps

I've recently enter my Restriction Code to turn OFF the delete apps function on my iphone. After I'd upated to 7.1, I enter the restricted code to turn ON some restriction and notice my Code was't working. I'd alway use the same old password!!! As for today its my 20th try. How could i forgoting my code in a few days.

Excellent point, sounds like the solution. It had seemed like a good idea to set the Restrictions passcode, but it's locked me out of Messages and FaceTime, even after upgrade and restore as we know. I've changed my passwords as per normal, and find I'm now locked out of Mail.

Anyone with this Restrictions Code issue, just try Gilsonmelo's excellent step by step instructions as it'll get the job done !

Thanks very much for the excellent tutorial &amp; fix !

This worked perfectly, I have my iCloud data and got finally rid off notifications from apps I don't care about. Thank you for suggestion!

interesting....i began having the same problem on 9/30 PM....totally frustrated with apple support at apple store. Came home..and about 3 hrs later....even after i rec'd the phone disabled msg(due to entering 'passcode' toooo many times........entered my usual pass code and it worked....able to get on home screen. tried on ipad....successful there to(but wasnt earlier...like iphone) Tried in the am of 10/1...and worked OK...and also noticed some type of update for IOS...and looked in the 'details'...and was for some fix the 'some users were having trouble with their passcode locks to get into main screen of phone). ran the update...still working good..........but about noon on 10/2.........quit working again..........began working about 2 hrs. later for 3-4 hours.....then quit.......not working till noon 10/3 then quit around 1pm 10/3....went BACK to apple store desscribed more and more..........and basically the zero'd phone, reloaded verizon software, and i came home to restore from backup. and they suggested NOT using the passcode feature 'for awhile'. REally?? my suggestion would be to keep trying...and if you get in...disable the passcode lock....and visit apple store to get the details of the status of the 'situation'. I tried going to 'chat' on apple.com....waste of time....never got on. I'm going to keep my sched. appt with tech at apple store tomorrow....will try to update later (sorry for the length of this...just totally frustrated).

Hey Gilsonmelo,

Thanks for you post! I used ibot and edited the plist and viola, my phone is now restored with restrictions passcode that i set. Interestingly, I had gone to the apple store and all the service guy told me was that if i just restore the iphone in itunes, it should be enough and can use my current backup. I guess the guy didn't know that the backup has the restrictions code bult in. And then i canme across this post by u. Thanks a ton! Really helped. 🙂

I'm thinking the update to iOS7 has done something to the restrictions on my iPad, as my son can now make in-app purchases which he couldn't do before the update and like others my restrictions password appears to have changed and none of my passwords work anymore! I think I'm going to have to wipe it and start again!

I was able to use these instructions to restore my phone, entering the restrictions passcode and turning restrictions off. After it fully restored I went back to restrictions and saw it was on again so I tried entering the restrictions passcode again and it's giving me the same wrong passcode error. Like it has reset again to something else although I did not change anything. Is anyone else experiencing this after restoring and does anyone know how to keep it from doing this again? Thanks for all the help.

I inputted what Gilsonmelo post about the plist but i can't save it. I say this because when i open the plist again there was no change from the original plist.

What to do?

THANK YOU! The default Restrictions Code is "0000" and was then able to turn it off.

Engineers developing and testing these updates need to be replaced!

I would like to know when apple are going to supply a fix for this restriction problem. I never set one and now I have one courtesy of the upgrade which I can't undo. Apple should be fixing this.

Took me two go's, but this has fixed the problem

Wonderful! It worked! Thank you gilsonmelo and timfrommoncton. I was constantly trying possible passcodes. Even ended up writing them down in a notebook so I'd remember what I'd already tried. Tried 93 different passcodes without success.

My notes to add were that I didn't know how to do a factory reset. Found out that you have to hold that home button down, plug it back in, and then wait for the itunes message to pop up. (I had been letting go of the home button too early -- at the apple logo.) After that, all was easy!

I did this on a 5s with ios7. Oh, and finding com.apple.springboard.plist wasn't easy. I finally found it for my phone under System Files - HomeDomain - Library - Preferences.

Hope this might help out the next guy!

Hello,

I've tried following your steps and checked everything in the codes, it all matches up, but the problem is that it won't let me save the code.

When I try and save the code it says "found non-key inside <dict> at line 93". That is because when I entered your code, it adds a line with the <string>1234</string> so the <key> is now at line 94.

Is there a fix for this?

Thanks, Jake