The RootHide development team has published a newer version of its Procursus-based bootstrap for non-jailbroken devices, this time pushing the package up to version 4.2 beta.
The latest version of RootHide’s bootstrap includes the following changes and improvements:
– Fixed the issue where Sileo prompts an error when installing packages (this is caused by other legacy /var/jb bootstrap that have been installed on your device before)
– Fixed the issue that tweak preferences cannot be saved in the TweakSettings app
– Add a check to see if the bootstrap app version is consistent with the currently bootstrapped environment
– Add prompt information about jailbreak detection
RootHide bootstrap v4.2 fixes bugs and focuses primarily on adding a feature that ensures uses are using a consistent bootstrap version with their environment. If it isn’t, users will see a prompt like the one shown below:
While the RootHide bootstrap allows for tweak injection (installing jailbreak tweaks) inside of apps, users can augment their user experience with a “semi-jailbreak” or more advanced tweak injection system called Serotonin, which allows for system-wide tweak injection.
There are risks for boot-looping your device with system-wide tweak injection if you don’t know what you’re doing or if a tweak malfunctions, so this is something to keep in mind. However, sticking with confirmed working tweaks and avoiding unnecessary changes to system files should mitigate this risk.
If you’re interested in learning more about the RootHide bootstrap, then you can head over to the project’s GitHub page. The bootstrap should be perma-signed with TrollStore 2 so it can utilize the kfd exploit and CoreTrust bug.
We should also advise that the recent release of a PPL bypass for iOS & iPadOS 16.0-16.5.1 means that a jailbreak will be coming soon to arm64e devices (A12+) on these versions, so you may opt to simply wait for that full-fledged jailbreak instead of using these hacks.
Are you running the latest version of the RootHide bootstrap? Let us know why or why not in the comments section down below.