Skip to content

Instantly share code, notes, and snippets.

@TheRealKeto
Last active November 7, 2022 07:25
Show Gist options
  • Save TheRealKeto/871116a9fc6cc46393b818816a876da0 to your computer and use it in GitHub Desktop.
Save TheRealKeto/871116a9fc6cc46393b818816a876da0 to your computer and use it in GitHub Desktop.
Documentation of most common errors you can encounter when using Futurerestore.

Futurerestore's Common Errors

When using Futurerestore in order to upgrade, downgrade, or re-restore to an unsigned fimrware, you may encouter some errors along the way. This is a "guide" that documents all of the most common errors you can encounter when using Futurerestore, and will show you how to solve them.

If you encouter an error that's not listed here, you may refer to r/Jailbreak, as this is only documentation with the most common errors you can encouter.

Error code -2: Could not put device into Recovery Mode

If you're on iOS 10 using the Meridian jailbreak, then you've probably encoutered this error when using Futurerestore. This is because the jailbreak itself, as it contains a "version" (rather binary) of ldrestart that is broken.

If you encounter this errors on iOS 10 using the Meridian jailbreak:

  1. Download Meridian from here, and sideload it with Cydia Impactor
  2. Set your nonce generator with Meridian, then proceed to use Futurerestore to upgrade, downgrade, or re-restore your device
  3. While your device is restoring, put your device into Recovery mode. You can do so by holding the Home + Power button, or by holding Volume down + Power button if you're using an iPhone 7.

This should allow your device to upgrade, downgrade, or re-restore your device using Futurerestore, and the restoration should successfully end (assuming you don't encounter any further errors)

On other firmwares

If you're not on iOS 10 and encouter this error, here's a list of things that can cause this error to occur when using Futurerestore:

  • Having NO PLS Recovery installed on your device can cause Futurerestore to not work propertly, or fail showing this error.
  • If you're using Windows, make sure that you connect your USB to Lightning Cable on a USB port that is directly attached to your motherboard. Failing to do can cause Futurerestore to not communicate with your device with this error showing up.
  • If you're using anything lower than macOS 10.13, upgrade to Mojave or Catalina on your PC (if possible). This is to ensure that your machine is on an OS that Futurerestore supports.

Error codes -8 & -10 (Unable to send iBEC/Place your device into Restore Mode)

If you encouter any of these two errors (or both), it's because you may not have iTunes and its drivers installed correctly. In order to fix these errors:

  1. Attempt to upgrade, downgrade, or re-restore your device and let Error code -8 appear.
  2. Head to "Device Managment" under "Control Panel"
  3. Locate "Apple Recovery (iBoot) USB Composite Device". This is often found at the bottom.
  4. Right click, then choose "Uninstall Device". It's best to also check off the option to uninstall the driver software as well.

All three Apple mobile device entries under "USB devices" will then disappear. At this point, unplug your device, then plug back in and attempt to upgrade, downgrade, or re-restore again. If Futurerestore still fails:

  1. Go back to "Device Manager" and repeat the driver uninstall process. (described above)
  2. DO NOT disconnect your device.
  3. Attempt to use Futurerestore again.

Futurerestore should work just fine after this (assuming you don't encounter futher errors)

More Troubleshooting

This section contains errors that are "relatively" small and don't require their own section, as they are fairly simple to fix. If you encouter any of these errors, follow the steps for the error you encoutered.

Error code -20: Device nonce does not match APTicket nonce

Make sure that your nonce generator is the same as the one inside your SHSH2 blob. If you've made sure that it matches your SHSH2 blob, re-set your nonce generator again. Do note that if your keep encoutering this error, then its safe to assume that your blobs are invalid, meaning that they are essensially useless and you can't use them to upgrade, downgrade, or re-restore to an unsigned firmware.

Error: Unable to receive message from FDR...

Make sure that the SEP and Baseband you use in order to upgrade, downgrade, or re-restore to is compatible with the version you're trying to get to. Failing to do so can cause this error to pop up. If you're unsure as to which baseband is compatible with your device, check out the Futurerestore guide, where its likely stated which IPSW you should get your SEP and Baseband from.

If your device is stuck on Recovery mode:

  1. Open Command Prompt/Terminal.
  2. Drag Futurerestore from your futurerestore folder (assuming that you followed the Futurerestore guide) onto your terminal.
  3. Type --exit-recovery.

This should kick your device out of Recovery Mode. Alternatively, if using Futurerestore doesn't work, you can use iMazing to do the same.

Lastly, if your device is stuck on the "Update Completed" screen after using Futurerestore, you can also use iMazing to bypass this screen on your device.

About this Guide

This guide was updated on October 7th, 2019, and continues to be updated. If you have any questions, contact me through Discord or head over to r/Jailbreak's Discord Server for support under their futurerestore-help channel.

@umaircodess
Copy link

umaircodess commented May 23, 2021

future restore stuck at "Unknown data request 'PersonalizedData' received" and phone is showing progress bar at about 50% and Its stuck here for hours. I have tried changing ios version , didn't help. I think my phone has a baseband problem, could that be the reason? also I can flash it fine with iTunes or 3uTools.
I am trying to downgrade ios 14.5.1 to ios 14.4.2/14.5. Neither is working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment