You can only save blobs for iOS versions that Apple is currently signing.

futurerestore -t blob.shsh2 --use-local-tss --no-baseband custom.ipsw

| Term | Meaning in Context | |------|--------------------| | (noun) | A local server that acts as Apple’s signing server using saved blobs | | shsh host (verb) | The act of redirecting or serving SHSH blobs via a custom hostname/IP | | /etc/hosts + SHSH | A technique to block or reroute Apple’s signing requests |

If shsh.host is down, you can use TSSSaver or Blobsaver .

Even if you have a valid SHSH host replaying perfect blobs, the restore will fail if the target iOS version’s SEP firmware isn’t signed anymore. Apple doesn’t allow SEP downgrades, so you’re forced to use the SEP from the currently signed iOS—which may break Face ID, Touch ID, or cellular.

So, what exactly is a ? The term refers to using a custom server, acting as a host for SHSH blobs, to bypass Apple’s official signing server. The most famous example is the Cydia SHSH Server , maintained by the developer Saurik.

To understand why a dedicated host is necessary, it is helpful to look at the security mechanism Apple uses during a firmware restore: How to Save SHSH Blobs for iOS 16 (Easy Guide)

Click the button to request and save. The site will fetch the digital signatures from Apple and store them on their servers for you.

After you click the button, shsh.host will go to work. It will contact Apple's signing servers and request the SHSH blobs for the iOS versions that Apple is currently signing for your specific device model.