Gbyte Unlock
Gbyte Unlock
Safely remove any iPhone/iPad screen lock in a few clicks.
Table of contents
"You can try your passcode again in null" is a display bug on the standard Security Lockout screen — the countdown failed to load, not a new or separate problem. Apple hasn't published anything explaining it directly. A restart often brings the timer back. When it doesn't, the same paths that unlock any Security Lockout screen apply here too.
Watching a lock screen tell you to "try again in null" is unsettling in a way a normal countdown isn't — there's no number to wait out, just a placeholder where one should be.
"Null" is a programming term for an empty or missing value. On this screen, it's standing in for whatever number of minutes or hours was supposed to display next to "try again in" — the system reached for that number and came up empty.
Worth being upfront about: this isn't something Apple has documented or named. Every explanation for it, including this one, comes from third-party observation and user reports, not an official source. The mechanism itself is a reasonable read of what "null" means technically, but nobody outside Apple can say with certainty why the display fails to load in the first place.
Where "null" shows up changes what it likely means.
Seeing it during what should be a timed wait — the kind of screen that would normally say "try again in 5 minutes" or "try again in 1 hour" — points to a display glitch. The countdown exists somewhere in the system; it just isn't rendering. The device is still in a temporary, recoverable state.
Seeing it after the device has clearly run out of attempts — no visible countdown at all, following a long string of wrong entries — points to something different. At that stage, there may be no number left to display because the device has moved past the timed-wait phase entirely and needs to be erased regardless.
There's no way to check this with certainty from the screen alone; a rough sense of how many attempts were made, and whether a countdown was showing before "null" appeared, is the best available signal.
A quick self-check:
Was a countdown ("try again in X minutes/hours") visible at any point before "null" showed up? → Points to a display glitch.
Has there been a long, continuous string of wrong passcode entries — more than eight or nine in a row? → Points to the device having run out of timed attempts.
Did "null" appear right after tapping "Erase iPhone," rather than on the initial lockout screen? → Also points to attempts being exhausted, since erasing wouldn't normally involve a countdown at all.
A force restart works regardless of what the lock screen shows — it's a hardware button sequence, not something that requires unlocking first.
Multiple independent reports describe restarting as effective specifically at refreshing a stuck or blank countdown display, getting the timer to show a real number again. What restarting does to the underlying attempt count is murkier: some sources describe it as having no effect on the security timer at all, while others describe it resetting the wait back to the start. These accounts contradict each other, and neither is an Apple-confirmed behavior — worth knowing rather than treating either claim as settled fact.
The practical takeaway: force restart, then look at the screen. A real countdown reappearing means waiting it out works as usual. Still showing "null," or nothing at all, means moving to the options below.
What "fixed" actually looks like: the lock screen should show specific text again — "try again in [X] minutes" or "try again in [X] hours" with an actual number filled in, not a blank space or a repeated "null." If the screen instead jumps straight to showing "Erase iPhone" with no timer at all, that's consistent with the device having exhausted its attempts rather than the restart having failed — the self-check above applies here too.
If the restart didn't bring back a real countdown, the diagnosis from earlier points straight to a fix: the passcode's age and what's available (an Apple ID, a computer) decide the route.
Your Situation | Recommended Method |
Passcode changed within the last 72 hours | Reset from the Lock Screen |
Apple ID password known, no computer nearby | Erase iPhone |
No computer, Apple ID unknown, or Erase iPhone unavailable | iTunes or Finder (computer required) |
A computer is available, guided steps are preferred | Third-party unlock software |
Best for: The passcode was changed within the past 72 hours.
Pros:
No data erased
No computer or Apple ID needed — uses the previous passcode instead
Limitations:
Only available on iOS 17 and later, within that 72-hour window
Past that window, this option leads to erasing the device instead
Still depends on the lock screen displaying and responding correctly
👉 See exactly how the 72-hour reset option works
Best for: The Apple ID password is known, and there's no computer nearby.
Pros:
No computer required
Can be done directly on the lock screen, or remotely via Find My from another device
Limitations:
Erases the device
Needs a network connection to complete — worth checking, since a device stuck on a broken "null" display may also be having trouble reconnecting to Wi-Fi after a restart
👉 Walk through the full Find My erase steps
Best for: A computer is available.
Pros:
Doesn't require the Apple ID
Has nothing to do with what the lock screen is or isn't displaying correctly, since the computer takes over once the phone enters Recovery Mode
Limitations:
Requires a computer
Erases the device
Windows and older Mac systems use iTunes; Catalina and later use Finder — both do the same job. Getting into Recovery Mode on iPhone 8 and later: quickly press Volume Up, quickly press Volume Down, then hold the Side button until the recovery screen appears. From there, iTunes or Finder offers a Restore option.
👉 Get the complete iTunes/Finder unlock breakdown
Best for: A computer is available, but you prefer a guided process instead of manually using Recovery Mode or Finder/iTunes.
Third-party unlock tools simplify the restore process by guiding you through device detection, firmware download, and screen lock removal steps. They are especially useful for users who are unfamiliar with Recovery Mode or encounter difficulties with Apple's official tools.
Pros:
Step-by-step guided workflow
Detects the device automatically, even when the iPhone is locked or unavailable
Easier alternative to manually entering Recovery Mode
Handles firmware download and restore steps in one place
Limitations:
Paid, not free
Erases the device
Requires a computer and USB connection
Tools like Gbyte Unlock handle device detection and the restore process without requiring prior Recovery Mode experience.
Method | Works Regardless of Lock Screen Display | No Computer Needed | Keeps Your Data | No Apple ID Needed | Cost |
Lock Screen Reset | ❌ | ✅ | ✅ (within 72 hrs) | ✅ | Free |
Erase iPhone | ❌ | ✅ | ❌ | ❌ | Free |
iTunes / Finder | ✅ | ❌ | ❌ | ✅ | Free |
Unlock Software | ✅ | ❌ | depends | ✅ | Paid |
The first column matters specifically for a "null" screen: the two lock-screen-based options still depend on that screen functioning correctly enough to tap through, while iTunes/Finder and third-party software bypass the lock screen's display entirely once the phone is in Recovery Mode — useful if the lock screen itself seems unreliable.
Check for a backup. Whether the data comes back afterward comes down to whether a recent iCloud or computer backup exists.
Use an original Apple cable for iTunes or Finder. Off-brand or charge-only cables are a common cause of the computer failing to detect the device.
Stay on a stable network connection for Erase iPhone. It won't complete without one.
Once back in, check for software updates. Settings > General > Software Update, and updating apps through the App Store, clears out bugs that may have contributed to the display issue in the first place.
"Null" on a lock screen is a rendering failure standing in for a number that should be there, not a new category of problem. A restart is worth trying first since it costs nothing and often fixes the display outright. Past that, the passcode's age determines whether there's a data-free way back in — and if there isn't, a backup made beforehand is what the rest comes down to.
No. It's consistent with a display bug on a standard security screen, not evidence of unauthorized access. Nothing about how "null" appears points to hacking specifically.
Not necessarily. It depends on which stage of the lockout it showed up in — during a timed wait, it's likely just a rendering failure; after attempts have run out entirely, the device may already be past the point where waiting helps.
Only if the passcode was changed within the last 72 hours, in which case the lock screen reset avoids erasing anything. Outside that window, every path back in requires erasing the device.
No. These are separate protections. Removing the passcode clears the lock screen; Activation Lock stays tied to whichever Apple ID was last signed in, and needs that account's cooperation, or Apple's official support process with proof of ownership, to release.
Since Apple hasn't documented this specific display bug, support staff are unlikely to have a targeted fix beyond the same steps here — restart first, then move to whichever unlock method matches the situation. Contacting Apple becomes worthwhile specifically when the Apple ID itself is the blocker, such as needing proof of ownership to resolve Activation Lock.
Add Gbyte as a preferred source on GoogleShare
Related articles
Copyright @2026 Gbyte. All rights reserved.
The installation wizard will automatically start after downloading.
After registration, the recovery process can be managed through the web interface.
You get it all with your purchase - no locked features, no hidden limitations.
