iOS 7 forgot restrictions passcode

Because you forgot the pass code you set? Have you called Apple?

My original issue is that Safari disappeared from my phone..than I started to investigate what could be the issue..I ended up here. I know all my pass codes, security codes and I definitely never set up any restriction code which is now blocking me from fixing the problem.

So I stuck here right now and I know that not having Safari is not a major issue but annoying and also my contatcs got messed up...my phone can not recognise who I am getting the messages from...showing only numbers instead of the names..I guess it is a different story but this came at the same time when Safari disappeared. I can not download it from AppStore either.

I guess I will need to go to a local service here in Europe.

Sounds like you or someone else inadvertently applied a restrictions pass code. I don't see why Apple would be at fault. Apple.co.uk/support

1111 worked for me!!!! try something similar ... i mean it probably was generated by default..

Thanks. I have tried 0000, now yours 1111, also 1234. No success. Now I got 60 minutes to think of another one. ((; As I am using the same 4 digits for all my numerical passwords..yes, I assume it got generated default.

There is no "default." You have to enter a code two times for it to set. Try pass codes that you think you would have used. Pins etc.

Please stop spouting your delusional crap. Are you somehow convinced that Apple's iOS contains no bugs? Why do you keep insisting that a forgotten passcode is the only possible explanation?!

Yes, a forgotten passcode is the only possible explanation. Let's hear another credible explanation.

Because as I said before, a variable isn't going to be changed and if it were changed it wouldn't be a RGN.

Well, as I've already suggested, if the memory where the passcode match (or it's hash, I have no idea how it's specifically implemented) were to get inadvertently overwritten due to a software bug, then the user would effectively be guessing a random number in order to know the passcode.

Similarly, if the 'restrictions passcode set' bit were set by a bug without the user actually ever setting the passcode, and the memory location were the match is stored were uninitialised, the result would be the same.

So there's a couple of credible explanations, unless you're of the view that software bug simple never happen.

I understand. No worries, I still like my phone. I truly beleive the issue will get solved somehow..as I also believe that I am not that dumb to spend hours on trying to fix something which would be about a forgotten password. Promise I will share it here, when I get to know the answer. For now, I will definitaley not hit the green stick on the right. Hope you don`t mind.

You are blowing smoke. Neither of those are credible. its only people who know nothing about information technology, cryptography or passcode management who can make this stuff up like you have. You are suggesting that somehow memory got corrupted in a 1+ GB OS image, and it only affected 1 bit, the Restrictions passcode? You have a better chance of winning the lottery than that happening.

There's no point in discussing it with you, because you wouldn't understand.

No, that doesn't make sense. The pointer would point to a specific number and it would be the same answer for everyone. If what you said is the case, everyone would have the same passcode.

rickwookie doesn't make sense and doesn't understand anything about computer technology. The best thing to do is to drop the discussion.

I'm not suggesting corruption. I'm suggesting a **** up in the code. It's a totally different thing. Hence why it's also totally repeatable.

You can try it yourself if you have an iPhone 4 on iOS 7 with no restrictions passcode ever set and therefore Restricions is off (I can't vouch for other devices as I've not tried it). Just go to Settings>General>Reset and select Reset All Setting. What happens for me is that Restricions is then On, with no way of knowing what code to use to access the restrictions settings.