Libiphone libiphone

Comments and changes to this ticket

• 

  Martin S. February 24th, 2012 @ 11:17 AM

  • State changed from “new” to “invalid”
  • Tag set to “boot, idevicerestore, nand, nor”
  • Assigned user set to “Martin S.”

  This is all working fine and as expected.
  The NOR/NAND writing is skipped correctly from what you describe. Mind that it is not only the baseband that is written here.
  If a specific iOS firmware upgrade requires a NOR/NAND write, it will only boot correctly if you restore without the "-x" option.
  If you update to iOS 5.0.2 for instance it might work to use "-x", on the other hand if you upgrade major versions (iOS 4 to 5), it will most likely always be required.
  In the newer models the baseband update appears to be separated from the initial NOR/NAND write, it might be possible to be able to actually skip only that specific part in the future.

• You flagged this item as spam.
  

  Ian Woods February 24th, 2012 @ 11:24 AM

  Thanks Martin.

  Is there a way of detecting if a particular firmware can't be restored with the -x flag set (other than hard-coding version numbering checks)? I may be able to add a simple check early in the process to warn/fail in those before putting the device into recovery mode.

• 

  Martin S. February 24th, 2012 @ 12:36 PM

  Not really, I think we noticed that sometimes you need the write even on minor upgrades so the new LLB is written to the device. The thing is, some iOS versions do not want to boot if you still have an old bootloader version.

  So this option is really just useful for restoring the filesystem to the device from the same firmware to basically reset it back to a post restore state and save time by skipping the NOR/NAND write process in the end.