How to solve the 16xx errors when restoring to a custom ipsw

The restore to a custom ipsw can prove to be quite problematic if your terminal is not jailbroken or is in Recovery/DFU Mode. If you make a custom ipsw with PwnageTool or sn0wbreeze and try to use it to restore a terminal in one of the situations presented above, you will definitely encounter errors like 16xx. Solving these errors is extremely simple and can be done by 2 methods, both of which involve entering the terminal into DFU Mode, so follow the steps below to enter the terminal into DFU Mode:

  • hold down the power button for 3 seconds;
  • without letting go of the power button, press the Home button for 10 seconds;
  • after the 10 seconds pass, release the Power button and the phone should already be in DFU Mode and redsn0w will start implementing the exploit.
  • if everything worked and the jailbreak was implemented then you should have this image displayed in redsn0w.

After you have entered the terminal in DFU Mode, you have 2 options.

1. Download any version of redsn0w for iOS 4.1 or higher by here. Load the iOS version corresponding to the downloaded redsn0w version then select Just Enter Pwned DFU Mode Right now. The terminal will be operated with limera1n and will allow loading the custom ipsw. After redsn0w finishes, you will be able to restore that custom ipsw. You can use this method for any iDevice.

2. Download the latest version of iREB ​​from here and follow the steps in the program to enter the terminal in Pwned DFU Mode. After iREB ​​finishes you will be able to restore that custom ipsw. You can use this method for times.

Either of the 2 methods is good, but I recommend the first one because I use it every time I load a custom ipsw. I recommend you bookmark this article if you use custom ipsws for restore.