6.1.3/6.1.4 A5+ Jailbreak status?!
As Apple closed the 6.1.3/6.1.4 signing window for devices capable of running iOS 7, many of you stayed behind on 6.1.3/6.1.4 (which is probably the best thing to do).
Everything for a 6.1.3/6.1.4 A5+ jailbreak is there. We're focusing on fixing bugs that occur internally. These range from Applications automatically deleting themselves from the uicache to iMessage/Facetime activations not working (even on legit sims). As far as a time frame goes for fixing these bugs, we have no idea. We're not lying. Its not like we got a progress bar going up every few minutes or something :P. I'll try to update this specific post as more things progress.
Does this also apply to A4 devices?
Yes, A4 devices will get the 6.1.3 untether alongside this release.
Some bugs that are occurring internally sometimes require the user to restore their device in iTunes. This obviously is not good if its an A5+ device as it will kick them out of this window of using the 6.1.3/6.1.4 jb.
Why don't you give ETAs?!
As I tweeted the other day, "Funny thing about ETAs: When one is said but failed to achieve, people get more rowdy than if no ETA was announced at all.". So with that being said, no date/ETA is being given. When its ready it'll be pushed. Again, we have no idea of any time frame as to when it'll get pushed. If anything, before 2014 :P.
Update #1 (Sept. 26, 2013): Looks like even more internal stuff is breaking. Still a work in progress.
Update #2 (Sept. 27, 2013): Added three more entries to blog.
Update #3 (Oct. 5, 2013): In the midst of polishing the 6.1.3/6.1.4 untether. While doing so, I requested people running 6.1.2 jailbroken devices to email me to dump their kernels for reference. In conjunction with that, I also requested people running 6.1.3/6.1.4 to email me as well. However, many seemed to have emailed me expecting to beta test the jailbreak. Not true, this was also for dumping kernels. I'm not sure why many people would want to beta test a jailbreak for an iOS Apple is not actively signing anymore anyways(if something goes, you'd be forced to restore to 7.x). Release is definitely not this weekend, so don't get your hopes up. ETA for it is before 2014. When release is close, we'll tweet it. (Please don't bother tweeting asking for an ETA/progress).
Update #4 (Oct. 6, 2013): Got every iPad 6.1.2 kernel dumped for reference (thanks to everyone who emailed!). Will be putting something together shortly to easily dump 6.1.3 kernels. When I need specific iPads on 6.1.3, I'll be sure to make a tweet. iPhones 4/4S/5 and iPod touch 5 6.1.3 kernels are already dumped, so those devices are not needed.
Why not keep these exploits for an iOS 7 jailbreak?!
They don't work on iOS 7.
iTunes 11.1 - WHAT IS THIS?! GO AWAY?!
Along with Apple pushing iOS 7, they updated iTunes to 11.1. This actually brought more headaches than convenience.
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". What this does is submit a request to Apple for an apticket + SHSH blobs. 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. 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.
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. 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). This essentially kills iOS 7 custom IPSW restores via iTunes.
Moving on to Error 11... This error seems to only be related to devices with basebands that require bbtickets (So basically the iPhone 4). 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 causes it to error out with code 11 (Error 11). It is worth noting that this issue was already present in the Mac OS MobileDevice framework on iTunes 11.0.x. When iTunes 11.1 was released for Windows, it looks like they finally merged code. Thus bringing the issue to Windows with iTunes 11.1. This does not affect the iPhone 3GS (bbfw is always pre-signed),
A temporary workaround to fixing Error 11 on Windows is by downgrading to iTunes 11.0.x. You can find download links to old revisions of iTunes over here (thanks cj!).
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. This is on my list of things to fix, but again... a workaround is typed up above.
sn0wbreeze/iFaith updates for iOS 7 please?!
As I have said above, iTunes 11.1 essentially kills iOS 7 custom IPSW restores via iTunes due to the "re-hashing" that is performed prior to the restore. I am working on a workaround for this, it will probably end up being something like the actual restore occurring within sn0wbreeze/iFaith itself (similar to redsn0w's "Restore" functionality).
As far as saving the iOS 7 apticket + SHSH blobs, iFaith can already fetch these blobs by selecting the "Show available caches on server" button and following on-screen prompts. This will work on all devices (including A5+ devices) except for the new iPhone 5C and iPhone 5S.
Dumping functionality to dump iOS 7 blobs+apticket on the iPhone 4 will come when I get around the silly iTunes issue sorted.
iOS 7 JAILBREAK PLEASE?!!! THX IN ADVANCE!
Before you start wanting an iOS 7 jailbreak, you should know that lots of things are currently broken in iOS 7. To list a few: Cydia, MobileSubstrate, and WinterBoard. Not really worth pushing anything at the moment until these issues are sorted out (please don't bug saurik to fix it. He is aware of it already).
With that being said, there is no use in pushing a user-friendly tethered iPhone 4 jailbreak at the moment.
As for updates on an A5+ iOS 7 jailbreak, follow the @evad3rs for updates on that.