Seas0npass ipsw install#
If you install this fix and it doesn't work for you then you can simply uninstall the fix and it will revert iTunes back to it's original state. This fix was tested on iTunes v11.1.1.11 but will more than likely work with any newer versions of iTunes until of course Crapple changes something else. I've created a "FIX" for the issue which will replace the problematic files with files from iTunes v11.0.5.5 and will allow you to restore Custom IPSW's to your device using iTunes 11.1.x.x without getting Error 11 messages. I know most people like myself have already updated to iTunes 11.1.x.x and would rather not be burdened with having to downgrade and have to redo their entire library. I have taken it from another site because I thought it was just too good to not share with iPhoneForums so enjoy! The person who wrote the post below in green is the one who shall take credit for this magnificent fix. This is on my list of things to fix, but again. One more thing worth mentioning is iREB for the iPhone 2G, iPhone 3G, and iPod touch 1G is broken with the iTunes 11.1 update. You can find download links to old revisions of iTunes over here (thanks cj!). This does not affect the iPhone 3GS (bbfw is always pre-signed),Ī temporary workaround to fixing Error 11 on Windows is by downgrading to iTunes 11.0.x. Thus bringing the issue to Windows with iTunes 11.1. When iTunes 11.1 was released for Windows, it looks like they finally merged code.
Seas0npass ipsw mac os#
It is worth noting that this issue was already present in the Mac OS MobileDevice framework on iTunes 11.0.x.
Seas0npass ipsw code#
This causes it to error out with code 11 (Error 11). Even though iFaith/sn0wbreeze removes the baseband requirement, iTunes 11.1 is expecting the iPhone 4 baseband firmware to be signed no matter what and notices that it isn't. This error seems to only be related to devices with basebands that require bbtickets (So basically the iPhone 4). This essentially kills iOS 7 custom IPSW restores via iTunes.
Meaning if 1 byte of any image is modified, when iTunes calculates the new "hash" and sends the TSS request, the TSS server will refuse to fulfill the request (Error 3194 is displayed). Now, prior to iTunes sending the TSS request to Apple, they ignore the values already in the BuildManifest and "re-hash" every image within the IPSW to create the TSS request. When tools like sn0wbreeze, PwnageTool, seas0npass, or redsn0w modified images such as iBSS, iBEC, ramdisk to avoid signature checks during the restore, iTunes didn't care or know. Previous revisions of the iTunes Mobile Device Library would just use the BuildManifest included inside of an IPSW to supply the request to Apple with the essential "hashes" of each image within the IPSW. What this does is submit a request to Apple for an apticket + SHSH blobs. When a user hits the restore button, they often see "iTunes will erase and restore your iDevice to iOS x.x.x and will verify the restore with Apple". This actually brought more headaches than convenience. For the jailbreakers, I'm sure you have read this message from iH8sn0w:Īlong with Apple pushing iOS 7, they updated iTunes to 11.1.
0 kommentar(er)
