Another iOS 7.0.2 lockscreen bypass bug found (with video)

MacDailyNews reader Hunter has found another iOS 7.0.2 lockscreen bypass bug.

“This is another ‘easier’ iOS 7.0.2 lock screen bug I have found,” Hunter told MacDailyNews via email. “It is very similar to the one found by Dany Lisiansky.” (See related article below.)

How to perform the bypasss:

1. Swipe to the passcode screen.
2. Press Emergency and Cancel at the same time.
3. Then swipe up and hold from the bottom left right after the screen switches to activate the camera.
4. Pull the Emergency Call pane down (keep holding the camera button) until you can type the number you want.
5. Then press call repeatedly until the phone reboots into the call.

Direct link to video here.

Related articles:
New lockscreen bug in iOS 7.0.2 allows any call from iPhone’s emergency screen (with video) – September 30, 2013
iPhone lockscreen can be bypassed with new iOS 6.1 trick – February 14, 2013


  1. With just about everyone you see walking the streets has a mobile phone, why would anyone bother going through all that just to get a free call? Crazy!
    Apple will close this in the next update for sure….

  2. It does not work if you follow the 5 steps above. The video shows many more steps. It looks like all of the “bypass bugs” are attempting to simply “overload” the phone by pressing and swiping a lot to provoke the phone into a reboot.

    Apple should probably fix this, but it seems like a lot of wasted time with very little results. Maybe some college kid is going to be a victim of a two hour phone call to India while he is passed out but other then something like that, don’t worry about it. If your phone is lost , contact your carrier to cut it off. Duh.

  3. All these thing are excellent real word tests for a rare occurrence. Apple will use all these things to improve the security of the iPhone. Sometimes many hands make light work. Hard to test all of this in the lab. There are lots of patient, obsessed folk out there. Go for it!

  4. Apple should reevaluate the entire lockscreen system and develop comprehensive strategy to actually keep it secure. The way it is now, with bugs like this popping up, getting patched, and getting replaced by new bugs, it seems like there’s just a hodgepodge of spaghetti code protecting the lockscreen.

      1. What? No one has coded on top of DOS for a very long time: Windows stopped running on top of DOS about the same time Apple stopped using Mac OS 9 / Classic. It makes zero sense to be comparing iOS in 2013 with Windows in the late 90’s.

        As much as Microsoft sucks, they have nothing to do iOS’s ongoing lockscreen issues. My only theory for your bizarre comment that you don’t know what spaghetti code means, have no idea what you are talking about, and just felt like mimicking others to mindlessly bash Microsoft.

  5. Again, like the last one, I could not reproduce the effect. However I have access to the pull up screen at the emergency window. I still don’t see the real problem, when in fact I have Siri active at the lock screen anyway.

    The real fix here, is to ensure that only 911 is available via the lock screen.. As a matter of fact, why not have a giant red button, labeled PANIC? to call 911?

  6. I’ve been able to reproduce this. Actually , it shows a weakness in Apple’s lock screen UI design where multiple panes seem to get confused about which one is currently active and they seem to merge together when doing this trick. It does feel “shaky” to me… Apple, fix it. Thanks. 🙂

  7. I learned years back to appreciate the hackers for finding this stuff. If they don’t you know damned well some cracker rat will, and use them. A lot of what feeds the robbery incentive is folks in the criminal market knowing how to make stolen stuff look new again. Once that happens, once there’s money being handed out by the stolen goods fences, the robbery rate skyrockets. It’s simple economics.

    Therefore, the sooner Apple knows the hacks, the better. And thank you to the hackers for discovering this stuff.

    HOWEVER! White Hat hackers turn their hacks into the affected source FIRST, then turn them over to the public AFTER a period of repair by the source.

    This jerk is a Black Hat hacker for making the hack public ASAP, to hell with the consequences. ‘Look at me. I’m so 1337.’ AKA insecurity over-compensation.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.