Download iOS 6.1.2 iPSW for iDevices
iOS 6.1.2 [10B147] [10B146] ipsw now available for download for iPhone, iPad and iPod touch, iOS 6.1.2 does not fix the passcode security flaw, but fixed the Exchange Calendar bug that could have resulted in “increased network activity and reduced battery life”. Hit the jump to download iOS 6.1.2 from direct download links…
How to update to iOS 6.1.2
iOS 6.1.2 update is now available via both iTunes and iOS software update panel. You can directly install this update via over-the-air or through one of the direct links shown further down in this post.
Note: Although Apple has already stopped signing iOS 6.1 and iOS 6.1.1, but don’t worry Jailbreakers as the evad3rs dev team has updated evasi0n to version 1.4. Later we will release the download link of evasion 1.4.
Download iOS 6.1.2 ipsw
Below are the direct download links for iOS 6.1.2 IPSW files for iPhone 5, 4S, 4, 3GS, iPod Touch 5G, 4G, iPad 4, 3, 2 and iPad mini…
- iPhone 5 GSM
- iPhone 5 CDMA
- iPhone 4S
- iPhone 4 GSM
- iPhone 4 CDMA
- iPhone 3GS
- iPad mini (GSM, CDMA, Wi-Fi)
- iPad 4th-generation (GSM, CDMA, Wi-Fi)
- iPad 3rd-generation (GSM, CDMA, Wi-Fi)
- iPad 2 (GSM, CDMA, Wi-Fi)
- iPod touch 4th-generation
- iPod touch 5th-generation
News on the bug fixes
Ars Technica reports:
The release notes only mention the Exchange issues, but we wanted to check to see if the passcode unlock bug from iOS 6.1 had also been fixed. We tried the convoluted unlock exploit on our own iPhone and were able to unlock the screen successfully under iOS 6.1.1, and the same process once again unlocked the phone in iOS 6.1.2. Put simply: it doesn’t look like this update fixes the passcode unlock bug, according to our testing.
We’re assuming that since Apple had acknowledged the issue, they would have mentioned it in the release notes if it was fixed.
If you’re worried about it, then you should set up disable “Simple Passcode” feature (Settings -> General -> Passcode Lock) on your iPhone and setup an alphanumeric passcode.
If you’ve upgraded to iOS 6.1.2, let us know if you have been able to replicate the bug.