![]() 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. It is worth noting that this issue was already present in the Mac OS MobileDevice framework on iTunes 11.0.x. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |