-
All replies
-
Helpful answers
-
Feb 20, 2014 3:42 PM in response to libikokaby ElRojito,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.
-
Feb 20, 2014 3:43 PM in response to ElRojitoby rickwookie,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?!
-
Feb 20, 2014 3:44 PM in response to rickwookieby Lawrence Finch,Yes, a forgotten passcode is the only possible explanation. Let's hear another credible explanation.
-
Feb 20, 2014 3:49 PM in response to rickwookieby ElRojito,Because as I said before, a variable isn't going to be changed and if it were changed it wouldn't be a RGN.
-
Feb 20, 2014 3:53 PM in response to Lawrence Finchby rickwookie,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.
-
Feb 20, 2014 3:56 PM in response to ElRojitoby libikoka,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.
-
Feb 20, 2014 4:01 PM in response to rickwookieby Lawrence Finch,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.
-
Feb 20, 2014 4:00 PM in response to rickwookieby ElRojito,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.
-
Feb 20, 2014 4:04 PM in response to ElRojitoby Lawrence Finch,rickwookie doesn't make sense and doesn't understand anything about computer technology. The best thing to do is to drop the discussion.
-
Feb 20, 2014 4:14 PM in response to Lawrence Finchby rickwookie,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.
-
Feb 20, 2014 4:26 PM in response to rickwookieby Lawrence Finch,I just did that with my 5S. If I had Restrictions passcode set BEFORE resetting all settings it prompted for the passcode I had previously entered and accepted it. If I had restrictions disabled before resetting it did not prompt, and when it completed the reset it did not set a Restrictions passcode. So most likely you had a restrictions passcode set and forgot that you had. As it's the same OS I would not expect it to behave differently on different devices.
-
Feb 20, 2014 4:45 PM in response to Lawrence Finchby rickwookie,Well I did stipulate to try it on a device where the restrictions passcode had never been set, but I appreciate that wouldn't necessarily be something you had to hand.
"most likely you had a restrictions passcode set and forgot that you had"...
The first time this problem arose for me was directly after upgrading to iOS 7. After following fte procedure mentioned earlier in this thead to set the restrictions passcode to a know pin using the restore procedure, I then was able to access the restrictions menu using that pin. I then switch off the restrictions lock. I then reset the settings (this was in the desperate hope of a settings reset making iOS suck slightly less on the iPhone 4, it didn't btw) and it was THEN that restrictions got set back on.
So, how likely is it actually that I forgot the code in those few seconds?! Particularly since I'd set it to a well used know pin, AND I could read that pin in plain text on my computer screen from the plist file.
-
Feb 20, 2014 5:10 PM in response to rickwookieby Lawrence Finch,It's much more likely that any other explanation you have put forth.
I just took a spare 4S and erased it to its new state (settings/General/Reset - Erase all content and settings.) I then set it up as a new phone. So it is now like a new out-of-the-box phone. No restrictions passcode, as that's the default for a new phone. I then did settings/general/reset - Reset all settings.
When the phone came back up it did not have a restrictions passcode set and Restrictions were still off.
-
Feb 20, 2014 5:59 PM in response to Lawrence Finchby damenfromtravis afb,"It's much more likely that any other explanation you have put forth."
No, its exactly as he put forth in his last reply. It also happened to me even though I had not set the passcode on my phone EVER. I am not tech illiterate nore do I have dementia and forget I set a code to my phone. I followed the suggested series of fixes stated earlier in this thread months ago after doing the update and after a day of cursing future iOS updates.
I didnt re-read all the back and forth, just this last page (I need to get me email off this thread for updates I do not care to clutter my inbox) but the rickwookie's last post is right on target.
-
Feb 21, 2014 7:49 AM in response to Richs79by libikoka,Hi All,
Just wanted to share that the code: 2222 worked for me. Thanks for the suggestions on trying this out!