It wasn’t too long ago that hacker and unc0ver lead developer Pwn20wnd released unc0ver v2.2.6 to the masses and dropped subsequent revisions to the unc0ver v3.0.0 pre-release for public testing, but Pwn20wnd is known for being quite the active developer and he appears to have revised the pre-release again since our last coverage with additional micro-updates.

According to the changelog published at Pwn20wnd’s official
GitHub repository, betas 18 and 19 of the unc0ver v3.0.0 pre-release comprise
of the ensuing changes:

02/06/2019 – v3.0.0~b18 was released for public testing with the following changes:

– Fix a theoretical bug in async_wake

– Fix a typo

– Fix a bug in device / firmware checker

02/06/2019 – v3.0.0~b19 was released for public testing with the following changes:

– Fix a logic bug in device / firmware checker

As it would seem, the latest revisions deal largely with preventing a ‘theoretical’ bug that could impact the performance of async_wake and known bugs impacting the device and firmware-checking features of the unc0ver app. Upon straightening those issues out, the tool should now function as designed.

At the time of this writing, the unc0ver v3.0.0 pre-release is still in its beta stages and should only be deployed by experienced jailbreakers or developers who understand the fundamentals of jailbreak-centric troubleshooting.

unc0ver v3.0.0 pre-release is the only version of this jailbreak tool that
supports iOS 11.4-11.4.1, but only on certain devices (A9/A9X/A10/A10X/A11). It
will install Cydia and supports Cydia Substrate on these firmware versions.

unc0ver v3.0.0 pre-release also sports partial support for iOS 12.0-12.1.2 on
certain devices (a limitation of the exploit used), but Cydia and Cydia Substrate are not yet fully compatible, and
so they will not be installed; SSH will be used instead. Those seeking a
full-featured iOS 12 jailbreak are advised to continue waiting.

The latest version of the unc0ver v3.0.0 pre-release is available to download from Pwn20wnd’s GitHub repository. Nevertheless, we advise that you refrain from using it until it’s officially out of its beta stages.