Despite being intended for older device and firmware combinations, iOS developer LukeZGD’s EverPwnage jailbreak tool has been receiving a lot of updates recently with support for more devices and firmware versions.
The latest update came over this past weekend, as EverPwnage received an update to version 1.3. The new update not only switches to a different exploit, but adds support for new firmware, along with adding several other improvements.
The full change log for EverPwnage v1.3 can be found below:
- Switch exploit to oob_entry. With this exploit, (re-)jailbreaking should never fail now
- Add support for iOS 9.3.5 and 9.3.6 (semi-untethered only, no untether)
- Add “Load Tweaks” toggle. This allows disabling tweaks on rejailbreak
- Allow reinstalling bootstrap on already jailbroken devices
- Updated IPA to attempt fixing an issue with A5(X) devices
Perhaps the most important change here is the switch to the oob_entry kernel exploit method by staturnzdev, which translates to 100% jailbreaking reliability for end users. This exploit doesn’t have a failure rate like many other exploits do, so it will work on the first go and keep working on every subsequent jailbreak attempt.
And that’s important, because the newfangled support for iOS 9.3.5 and 9.3.6 is semi-untethered, which means that after every hard reboot, users will need to re-jailbreak their device. This becomes less of a hassle when the exploit doesn’t fail, as you won’t waste as much time getting back into a jailbroken state.
Other changes in this update include a new Load Tweaks toggle so that users can easily disable their jailbreak tweaks on re-jailbreak for troubleshooting purposes and the ability to reinstall the bootstrap on already jailbroken devices, also for troubleshooting purposes.
The EverPwnage jailbreak tool is intended for 32-bit devices running iOS 8.0-9.3.6 only. Some device and firmware combinations support an untethered jailbreak, but others are semi-untethered. You can learn more about the jailbreak and download a copy for yourself from the project’s GitHub page.