ultrasn0w 1.2.8 and problems with iPhone decoding

  This week the solution of untethered jailbreak named evasi0n was officially launched, and along with it came a long-awaited one update for ultrasn0w, version 1.2.8 is now available in Cydia. Although many terminal owners iPhone 3GS si iPhone 4 they expected to decode their terminals with old basebands, unfortunately ultrasn0w 1.2.8 it doesn't do it right for everyone. More exactly, ultrasn0w 1.2.8 it does not decode most iPhones, even though they have old basebands and the problem seems to be from the new iOS released by Apple.

  The Dev Team updated the program without much fanfare, although normally they would officially announce this, and this gave me something to think about. Seeing that users cannot decode their devices, it was clear that somewhere in the middle there is a problem and unfortunately it affects many people. At the moment, those who had tethered jailbreak on iOS 6.x and used ultrasn0w fixer together with ultrasn0w, must completely uninstall the fixer and ultrasn0w, reset the terminals and only then try to reinstall ultrasn0w in order to make it functional. Custom ipsws made with sn0wbreeze seems to be a source of problems for ultrasn0w, many of those who have used this method to update to iOS 6.x have noticed that they cannot use ultrasn0w.

  If even after a new restore you cannot use ultrasn0w on iOS 6.x, then it is advisable to wait for a possible new update. It has been said since a few months ago that the use of old basebands on new versions of iOS is problematic, and now we see exactly what this means.