Skip to content
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.

Troubleshooting

Jump to bottom
RossDarker edited this page Feb 1, 2023 · 12 revisions

Troubleshooting

./prepare :

Could not connect to Github or IPSW.me - See Troubleshooting

This usually occurs if curl cannot establish a secure connection to one of these sites

  • Check internet connection
  • You may need to update curl with Homebrew/MacPorts if you are using an older version of Mac OS X:

./patchipsw :

Couldn't connect to device, install OpenSSH from Cydia, or run: rm ~/.ssh/known_hosts, then try again.
  • If the solutions in this message do not solve the issue, first try to ssh into the device normally:

ssh root@<IP address>

  • If anywhere you see something like this:
Unable to negotiate with <IP> port 22: no matching host key type found. Their offer: ssh-dss

... you'll need to edit your ssh config file:

  • On macOS run: touch ~/.ssh/config then open ~/.ssh/
  • Open the config file in TextEdit and add these lines (file may be empty) :
Host <IP address>
	HostkeyAlgorithms +ssh-dss
  • replacing <IP address> with the one of your iOS device
  • ssh should now work. For Windows, see this page

./enterkdfu :

IF YOUR DEVICE DID NOT TURN OFF, SEE TROUBLESHOOTING

Observation: device doesn't turn off when expected.

  • If you're on iOS 7.1.x, you'll need to update to the latest Pangu untether (v0.3) to enable tfp0 in order to enter kDFU mode:
    • Download the deb package for this here
    • Install on the device using iFile/Filza/Terminal or any other way to install deb packages

./dumpblobs:

ERROR: Blob for LLB is invalid (crypto)
myblob.plist is BROKEN

This is common but normal and seems to happen on macOS

  • Blobs have been fine despite this error: they have been used for successful restores without issue
  • Appears to be due to expired certificates, see this for more info
Did NOT succeed. First try running ./dumpblobs again (entering kDFU again if needed - usual fix), otherwise try on a different version of macOS.

The script wasn't able to dump blobs

  • Try entering kDFU and running ./dumpblobs again first

  • If the issue persists, inspect the Downloads/blobs/odysseus-0.999.0 folder

  • Enter the folder corresponding to your platform: macos/win

  • If myblob.dump exists but is zero bytes, something has gone wrong. This happens on Windows for certain configurations:

    • Issue has been described here
    • While running this natively in Windows would be ideal, a workaround solution that has worked for some Windows users has been to run a macOS VM, making sure to pass through the USB correctly.
    • The macOS version has been out since April 2019 and used over and over with lots of success

  • If you are having problems on macOS, make sure you are following any instructions on-screen during the ./dumpblobs process, such as unplugging and reconnecting the device - ensure the device is properly connected again

    • The backlight should come on too when you reconnect
    • Submit a log of your entire Terminal window along with your macOS version if issues persist
Clone this wiki locally