 |
Available In: Cydia |  |
Price: Free |
It seems that while we were on vacation, ultrasn0w was updated to version 0.9. The Dev-Team has quite a bit to say about this version of ultrasn0w (including how the source code from the purplesn0w unlock helped improve ultrasn0w…interesting). Anyway, below are just a few snippets from the post three days ago and the one from tonight.
Tonight:
It looks like version 0.9 of ultrasn0w fixed up the vast majority of any problems people were seeing with the 3G/3GS carrier unlock. But here’s a brief list of fixes for anyone still seeing problems:
• Unusual battery depletion is almost always caused by people choosing to “Restore from backup” instead of “Setup as new iPhone” when iTunes asks you. This isn’t caused by either the jailbreak or the unlock, but it’s a common 3.0 snafu. The fix is to just re-run the official 3.0 restore and choose “Setup as new” this time. Your music and apps and all that will still be synced, but you’ll get rid of any conflicting wifi, bluetooth, or carrier settings. Then just re-run redsn0w and install ultrasn0w.
• Remember, ultrasn0w works with hacktivated phones too, but don’t outsmart redsn0w into thinking you don’t need hacktivation! If you don’t plan on using an official sim, don’t activate via iTunes with such a sim. Just keep your unofficial sim at all times and let redsn0w and ultrasn0w handle hacktivation :)
• T-Mobile in the USA doesn’t use the 3G frequencies that the iPhones support, so turn off 3G in Settings->General->Network. (Some T-Mobile territories gracefully hand down to Edge mode, but most do not).
• Certain unofficial plans have limitations on whether you can make calls and use data at the same time. That’s not unlock-related.
• Some people have installed previous versions of ultrasn0w using non-standard techniques. While the ultrasn0w 0.9 update should have removed all previous versions of ultrasn0w, these users may have outsmarted our removal. So make sure you don’t still see /usr/bin/ultrasn0w present if you’re at ultrasn0w 0.9 (which doesn’t have such a binary anymore).
• If you don’t need or plan to update to ultrasn0w 0.9 from a previous version, you can avoid having that red badge over Cydia by removing repo666 as a Cydia source. Don’t worry, you can always add it back later :) If you follow us on twitter you’ll be advised of any new updates anyway.
Last but not least, many thanks to our resident blog moderators, angiepangie and Confucious. They’re doing a fantastic job helping people in the comments, and so are other volunteers. Thank you all for your contributions!
3 Days Ago:
Short Version:
ultrasn0w version 0.9 is out! We believe it solves pretty much all of the various random issues that have been reported. Its features include:• Works on both 3G and 3GS
• Works on hacktivated devices
• Works regardless of how you jailbroke your device
• Doesn’t patch any mach-o binary whatsoever. (Doesn’t require a separate patch as each new firmware comes out).
• Doesn’t install any additional daemon
• • Has no race conditions, no popups about “Missing SIM”, no network issues
• Is almost 7000 times smaller than its nearest competition :)
• Is available now via Cydia. Source repo is http://repo666.ultrasn0w.com (that last “0” in ultrasn0w is a zero!)Long Version:
The day before yesterday, some fellow named geohot released a program called “purplesn0w” which claims to be a better unlock than our ultrasn0w unlock released last month, and our yellowsn0w unlock released 7 months ago. He was kind enough to provide source, which we naturally took apart to try to validate his claims. ;)We’ve found he had come up with two pretty neat ideas, one more pragmatic than the other for the iPhone. The first is a way of patching the actual text of the baseband code by copying it over to RAM and then using the MMU and page tables to have the baseband pretend it is part of the original bootrom.
Loading...
Loading ...