iPhone Dev team has just released a new version of Redsn0w – Redsn0w 0.9.9b6, which includes a fix for the locations services issue reported by iPhone 3GS users with 06.15 baseband and cosmetic fix for iOS 5 jailbreakers.
Dev team has provided the following details on their blog:
We’ve released version 0.9.9b6 of redsn0w, with both a functional fix and cosmetic fix for iOS5 jailbreakers. For iPhone3GS owners with the 06.15 baseband, this redsn0w eliminates the network crash you saw when using Location Services in iOS5 (in fact, you don’t even need to disable Location Services anymore during the initial setup). The cosmetic fix is to the visual countdown you see when going into DFU mode.
It’s okay to re-run this redsn0w over an existing device jailbroken at iOS5. Just choose “Jailbreak” again and de-select Cydia (in other words, all the checkboxes will be unchecked). If you are lucky enough to have an old-bootrom iPhone3GS, please pre-select the IPSW first (redsn0w can’t yet auto-detect the FW version of your old-bootrom 3GS if it’s already been jailbroken).
Redsn0w 0.9.9b6 supports the following iOS 5 devices:
Redsn0w 0.9.9b6 supports only a tethered jailbreak, except for iPhone 3GS with old bootrom which is untetherd. With a tethered jailbreak you need to connect your iOS device to the computer on every reboot. It still doesn’t support iPad 2 and Apple’s new iPhone 4S.
If you need help, you can checkout our step-by-step guide to jailbreak iOS 5:
- How to jailbreak iPhone 4, iPhone 3GS running iOS 5 using Redsn0w
- How to jailbreak iPod touch 4G, iPod touch 3G running iOS 5 using Redsn0w
- How to jailbreak iPad 1 running iOS 5 using Redsn0w
Note: We’ll update the tutorial to incorporate the changes included in Redsn0w 0.9.9b6.
If you’ve already jailbroken your iOS device running iOS 5 then all you need to do is rerun this version of Reds0w. As always, let us know how it goes and if it has fixed the issues with location services.
Dev team hasn’t provided any update or ETA for the untethered jailbreak for iOS 5 nor the fix for the iBooks issue.
[via Dev team’s blog, Thanks Goranms for the heads up!]