Troubleshooting

For support in English, ask for help on the r/Jailbreak Discord Server.

TIP

If you're looking for troubleshooting palera1n issues, you should take a look at palera1n Troubleshooting

Bootloops and respring loops

Respring Loops

A respring loop is a symptom of an incompatible tweak(s), causing the device to be stuck in resprings while in a jailbroken state.

While there is no easy way to diagnose what causes a respring loop, the most likely culprit is your most recently installed/updated tweak being incompatible with your iOS version or another tweak.

Semi-(un)tethered jailbreaks

TIP

A semi-tethered jailbreak is a jailbreak that needs an app on a computer in order to jailbreak after a reboot.

A semi-untethered jailbreak is a jailbreak that needs an app that is installed on the device or website in order to jailbreak after a reboot.

In order to escape the respring loop, force reboot your device. Once you've booted back up, use your jailbreak of choice and disable tweak injection from the jailbreak settings. Once you've jailbroken, you should be able to access your package manager and remove your most recent tweak or your last tweak setting change that may have caused the respring loop.

In a worst case scenario, where you cannot diagnose or fix the issue, ask for support in the r/jailbreak discord serverOpen in new window or restore rootFS.

Untethered jailbreaks

TIP

A untethered jailbreak is a jailbreak that persists after a reboot

A respring loop on an untethered jailbreak is very easy to confuse with a bootloop, since even restarting your device will keep you in the respring loop.

In order to escape a potential respring loop, you must forcefully reboot your device and hold Volume Up, as the timing varies depending on jailbreaks, your best bet is to hold Volume Up until you've booted into iOS.

Even after you've attempted to do this multiple times, you may find that you cannot boot into iOS while holding volume up; you may be in a bootloop.

Bootloops

A bootloop is an unrecoverable error caused by either corrupted system files or a hardware failure. While much rarer in modern iOS versions, it is still possible to bootloop your device through accidental or intentional means.

A bootloop can be diagnosed by looking for a constant re-occuring Apple logo, even after you've forcefully rebooted your device.

In order to escape from a bootloop, you must DFU restore your device.

How to enter DFU mode

For devices with a real home button (iPhone 6s and below):

  1. Hold down both the Home button and Lock button.
  2. After 8 seconds, release the Lock button while continuing to hold down the Home button.

For iPhone 7/7+, iPod 7th Gen and 2018 iPads:

  1. Power on your iPhone/iPad if it's not on already
  2. Connect it to your computer with your cable
  3. Launch iTunes (or Finder on macOS Catalina and newer) and check that the iPhone/iPad is recognised
  4. Hold down both the Side button and Volume Down button.
  5. After 8 seconds, release the Side button while continuing to hold down the Volume Down button.

For devices without a home button, iPhone 8/8+, iPad Air 5 and iPad Mini 6:

  1. Power on your iPhone/iPad if it's not on already
  2. Connect it to your computer with your cable
  3. Launch iTunes (or Finder on macOS Catalina and newer) and check that the iPhone/iPad is recognised
  4. Press the Volume Up button immediately followed by the Volume Down button
  5. Press and hold down the Power button until the screen turns black
  6. Release the Power button
  7. Hold down the Power button and the Volume Down button for immediately after for 5 seconds
  8. Release the Power button but keep holding down the Volume Down button for another 5 seconds

How to exit DFU mode

For devices with a real home button (iPhone 6s and below):

Hold the Home button and the Lock button until the device reboots.

For iPhone 7/7+, iPod 7th Gen and 2018 iPads:

Hold down the Side button and Volume Down button until the device reboots.

For devices without a home button, iPhone 8/8+, iPad Air 5 and iPad Mini 6:

  1. Quick-press the Volume Up button
  2. Quick-press the Volume Down button
  3. Hold down the Side button until the device reboots.

Common Errors on Chimera, Odyssey, and Taurine

ERR_Jailbreak

DANGER

If you are seeing this issue while using taurine-permanent, follow ERR_Jailbreak when using taurine-permanent instead.

This is caused by you having used a previous jailbreak. To solve this, you need to restore rootfs:

  1. Reboot the device.
  2. Open the Odyssey or Taurine app, depending on your iOS version.
  3. Toggle the Restore Rootfs option
  4. Press the Jailbreak button.

Once the restore rootfs successfully completes, try jailbreaking again.

ERR_Already_Jailbroken and ERR_KernRW (Taurine)/ERR_TFP0 (Odyssey)

ERR_Already_Jailbroken indicates that the jailbreak process was interrupted. ERR_KernRW and ERR_TFP0 indicate that the exploit failed. Both can be solved in the same way:

  1. Reboot the device.
  2. Open the Odyssey or Taurine app, depending on your iOS version.
  3. Press the Jailbreak button.

TIP

Jailbreaks are hardly ever 100% successful, you may need to re-attempt running the jailbreak multiple times

"Installation Error" upon opening Sileo after initially jailbreaking on Odyssey 1.4.2

Remove the currently installed version of Odyssey, sideload the 1.4.1 version of OdysseyOpen in new window, and then restore rootfs and then rejailbreak.

Unable to open NewTerm or Cr4shed (among other things) after a period of time on Taurine

TIP

If you're on 14.3 or have an A12 or newer device, you likely either rebooted (which would mean you're no longer in a jailbroken state) or you may have something else causing issues entirely unrelated to the jailbreak.

If you're on 14.0 to 14.2 and have A11 or earlier device, this issue is caused by the fact that some tweaks and apps use libaries which have components that may run before the jailbreak is able to stop codesigning. When this happens, affected tweaks and apps cannot be used.

The easiest solution to this issue is to reboot and rejailbreak when this issue happens. Alternatively, if you do not want this issue to happen, you can jailbreak with Odysseyra1n, as Taurine and Odysseyra1n are both intercompatible with eachother, and Odysseyra1n is not affected by this issue.

ERR_Jailbreak when using taurine-permanent

Update to the latest version of taurine-permanent.

Sileo not appearing upon initially jailbreaking on Chimera 1.6.1 or Taurine 1.1.2

Common Errors on unc0ver

General issues with unc0ver on iOS 14

TIP

While these issues are generally the most frequent on iOS 14, some issues could be present even on earlier versions of iOS

While using unc0ver on iOS 14, it is very common to run into the following issues:

  • Apps hanging when trying to launch them
  • Various app store related issues (including the inability to download apps or make in-app purchases)
  • Being unable to receive phone calls while jailbroken
  • Having issues utilizing cellular data (such as being unable to load web pages or other online services)
  • Being unable to save, take, or view screenshots
  • Safari not loading pages, or reloading pages infinitely
  • The share sheet not functioning properly
  • Issues connecting to Carplay.

WARNING

If you are using Fugu14 to have unc0ver be permanently signed, you may experience these issues to a larger extent, as well as some Fugu14 exclusive issues, such as:

  • The inability to view battery statistics
  • More frequent and random kernel panics

To temporarily resolve these issues, userspace reboot by typing launchctl reboot userspace into a terminal app (e.g. NewTerm) on your device.

rootFS already mounted

  1. Open the Settings application
  2. Go to General -> iX Storage
    • This could be iPhone Storage, iPad Storage or iPod Storage
  3. Scroll to the System Update downloaded and tap on it
  4. Tap Delete
  5. Re-run unc0ver

If this doesn't fix it, or there is no update downloaded, you may need to download the OTA update and delete it again. Try the following instructions:

  1. Open the unc0ver application
  2. Tap on the settings icon in the top right-hand corner
  3. Uncheck all the options
  4. Enable Restore RootFS
  5. Press Done in the top right-hand corner
  6. Go to the jailbreak tab and press Restore RootFS
    • If the button says Jailbreak, go back and check to see if Restore RootFS is the only option enabled
  7. When prompted about restoring, tap OK
    • This may take some time
    • If it fails, try again from the beginning
  8. When finished, tap OK again, and your device will restart
  9. Open the Settings application
  10. Go to General -> Software Update
  11. Download the software update but do not install it
  12. Go back to General
  13. Once downloaded, go to iX Storage like before
    • This could be iPhone Storage, iPad Storage or iPod Storage
  14. Scroll to the System Update downloaded and tap on it
  15. Tap Delete
  16. Scroll to the unc0ver application and tap on it
  17. Tap Delete
  18. Install unc0ver again like before but don't run it yet
  19. Turn on Airplane Mode and run the jailbreak now
    • This may take several attempts, keep trying until it works

TIP

If this doesn't work, ask on the r/Jailbreak Discord ServerOpen in new window for support.

Not being able to rejailbreak or restore rootfs in unc0ver after using tweaks such as Batchomatic or IAmLazy

Your ability to fix this issue if you end up in this state depends on your iOS version:

  • If you are on iOS versions at or below 14.3 (excluding if you're on 11.x or are A12(X) 12.1.3-12.4.1), follow another jailbreak's Restoring Rootfs method that is supported on your device/version combination.
  • If you are on iOS versions 14.4 to 14.5.1, attempt to restore rootfs in the Fugu14 app
  • If you are either on iOS versions 14.6 to 14.8, or in the group excluded from the first group, your only options are to wait for another jailbreak, wait for an unc0ver update which fixes this issue, or to DFU Restore to the latest iOS version and lose your ability to jailbreak for the forseeable future

Fixing package installation errors on Sileo

For the purposes of this troubleshooting section, we are assuming you are running Sileo on Taurine/Odyssey/Odysseyra1n.

In order to determine which error you are encountering, you will have to tap Show Details in Sileo when you encounter an error with installing or removing a package.

If the fixes below don't help, feel free to ask on the Sileo Discord ServerOpen in new window for support.

Syntax error: "(" unexpected

This error indicates that the developer of the tweak you are trying to install/remove has written the installation/removal script incorrectly. You will need Filza to fix this issue.

Removing the tweak causing this error

  1. Open Filza and navigate to /Library/dpkg/info
  2. Find the .postinst or .postrm file corresponding to the tweak with an error, e.g. com.miro.shortmoji2.postinst would be the file to edit if ShortMoji 2 had an install error or com.miro.shortmoji2.postrm if it had an uninstall error
  3. Tap and hold the file until a menu appears
  4. Tap Open with
  5. Tap Text Editor
  6. Find the first line of the file that says #!/bin/sh
  7. Change sh to bash
  8. Tap Save
  9. Open Sileo
  10. Uninstall the tweak.
    • For paid tweaks, you will need to file a bug report to the developer if you wish to install the tweak.
    • For free tweaks, you should file a bug report to the developer. If you wish to install the tweak immediately, continue with this guide.

Editing the tweak to fix the error (Free tweaks only)

  1. Open ParcilityOpen in new window in Safari on your device
  2. Search for the tweak you wish to install
    • If it does not appear in the search, you will have to wait for the developer to update their tweak
  3. Tap Download
  4. Once the file has finished downloading, tap on the file in Safari's downloads menu
  5. Tap the share button
  6. Tap Save to Filza
  7. Tap Save
  8. Open Filza, it will open to the folder where you downloaded the tweak file
  9. Tap on the tweak you wish to fix
  10. Scroll down and tap Extract
  11. Open the result folder, and navigate to DEBIAN
  12. Repeat steps 2-8 of Removing the tweak causing this error above
  13. Navigate back to the folder where you downloaded the tweak
  14. Tap and hold on the tweak folder
  15. Tap on Create DEB
  16. Tap and hold on the resulting deb file
  17. Tap Open with
  18. Tap on Sileo
  19. Tap Get

TIP

Some developers in the Jailbreak community put a call to the wrong shell in their installation/removal scripts. Until April 2021, most Jailbreaks pointed /bin/sh to /bin/bash so developers were able to use #!/bin/sh to indicate which shell to use even if they use Bash features. In April 2021, Procursus, which runs on Chimera, Odyssey, Taurine, and Odysseyra1n, changed to a different, higher performance shell. This broke these incorrectly formatted scripts.

Exec format error

This error indicates that the developer of the tweak you are trying to install/remove has omitted a key part of the installation/removal script. You will need Filza to fix this issue.

Removing the tweak causing this error

  1. Open Filza and navigate to /Library/dpkg/info
  2. Find the .postinst or .postrm file corresponding to the tweak with an error, e.g. com.miro.shortmoji2.postinst would be the file to edit if ShortMoji 2 had an install error
  3. Tap and hold the file until a menu appears.
  4. Tap Open with
  5. Tap Text Editor
  6. Add a new line to the start of the file that says #!/bin/bash.
  7. Tap Save
  8. Open Sileo
  9. Uninstall the tweak.
  10. Navigate to the Sources tab
  11. Swipe down and refresh your sources
  12. Navigate to the Search tab
  13. Type libiosexec1 into the Search field
  14. Install libiosexec1 by Hayden Seay
  15. Try installing the tweak causing an error again

TIP

In May 2021, Procursus attempted to migrate to a version of dpkg that no longer handles this install error, as developers should have included the #!/bin/sh or #!/bin/bash calls in their scripts. At the time of writing, the lead developer of Procursus has created a patch, libiosexec, that re-adds this error handling. If you still encounter this error, you may not have updated for a while.