Back in February, iPhoneUnlockUK was hacked and 21,000 customers had their emails and other details compromised.

The hacker has now gone ahead and sent the 21,000 customers an email explaining that iPhoneUnlockUK have stole the program and were selling it illegal and therefore should demand their money back from them.

The company claim they are not doing anything wrong as they are providing extra services in exchange for the payment as well as the program such as technical support but in the eyes of the Dev Team it is still wrong.

Therefore, if you have paid a company for software to unlock your iPhone, you should demand your money back as they do not have the right to sell it and are selling it illegally.

Do not pay for unlocking software, Ultrasn0w is available for free HERE.

If you have an iPhone with 05.1107 (ie doesn’t work with Ultrasn0w) and want to unlock it, use Blackra1n.

• 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 an

Hope this helps people who are problems!

Ultrasn0w….

• 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!)

Here is the Dev Teams long post explaining exactly why their unlock is better than GeoHot’s:

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. Of course, like yellowsn0w and ultrasn0w, this code has to be reloaded with every reboot of the baseband. However, the advantage of this is that developing unlocking payloads is a lot simpler… in fact, geohot used the same payload in AnySim and BootNeuter. We kicked around this idea ourselves before, but eventually found a work-around for the same problem with the yellowsn0w/ultrasn0w payload. The two pieces of code have the exact same effect on the baseband… with the difference that geohot’s exploit overwrites an arbitrary block of memory one megabyte in size. The baseband has a total of eight megabytes of memory and every bit of it is earmarked for use (except for 485212 bytes of it which we haven’t accounted for yet, but that’s still less than 1 MB). This means that eventually the area of memory geohot is using will be corrupted and 1 MB of baseband code will be corrupted (until the next reboot). How soon will this happen? Will it even matter in day-to-day use? We don’t know, because we haven’t spent much time looking. However, why take the risk when the yellowsn0w/ultrasn0w payload accomplishes the same job with no corruption?

To put it into perspective, ultrasn0w uses 152 bytes of properly malloc’d baseband RAM, which is 0.015% of what purplesn0w uses.  Put another way, purplesn0w uses 6900 times more RAM than ultrasn0w (and doesn’t let the O/S know that it’s using it, so the O/S still thinks it’s free to use.  When it does use it, the baseband will crash).

Now, the second new idea he had was to patch CommCenter rather than use a daemon. At first, this idea seemed pretty distasteful to us. Binary patches are messy and difficult to maintain (we figure it’s partly why he only made a version for 3G S and not 3G as well). In addition, the stated reason of reduced battery life with a daemon is factually incorrect, since any computer science student who’s taken a course in operating systems will tell you that a sleeping task takes up exactly NO CPU resources and NO power (it’s merely skipped over during context switches). That’s right: not “only a little” power, but absolutely NO power. However, ultrasn0w 0.6 did have a problem where the STK refresh command it used crashed the baseband in 3G S. This caused the baseband to continually come up and then restart. That DOES take power and so may explain the issues that people have been seeing. ultrasn0w 0.8 was supposed to have fixed this issue, but perhaps not completely. This is because the STK refreshes we used are inherently unreliable… but we thought they were necessary to avoid people having to reinsert their SIM. Turns out we were wrong on that score. geohot’s method shows that we can perform the unlock before CommCenter polls for lock state. When we do it before (instead of after), the STK refreshs are no longer necessary! The only way to do it before the polling, however, is to modify CommCenter.

We’ve tried to make the best of a bad situation by using MobileSubstrate to perform the modification. This lets us modify the behavior of CommCenter without touching the actual binary. We also used a method to dynamically locate the patch location so that it should work on both 3G and 3G S (and should need to be updated less frequently). We also do it in a different way so that hactivated phones will work with the unlock (unlike purplesn0w). You’ll find that this update is now available through Cydia as ultrasn0w 0.9 We thank geohot for contributing to the scene once again. We don’t think purplesn0w is the right path, but it has certainly helped us improve ultrasn0w!

P.S. geohot, seriously, stop dicking around and look at the bootrom instead kthx. =P

Via

PoweryBase claim that when you use Push notifications, the iPhone contacts Apple’s servers to obtain a Unique ID to make the connection for Push notifications and the server are not giving the unique ID to 3rd party unlock phones.

When the Push based application such as NotifyMe requests an ID from APNS, the server responds within a second and identifies the device with the unique token. From that point, the connection between APNS and user’s device is successfully established,” said Pavel Serbajlo, PoweryBase’s lead developer. “However, on a unofficially activated device, APNS keeps the application wait forever and does not provide any respond at all, keeping user wait infinitely or time out the connection, if the target application is capable of timing out.

PoweryBase have recommended people with unlocked iPhones to not download any push enabled appilcation until a fix is found.

Dev Team have announced on their Twitter that they are working on a fix but for now, do not download push enabled app if you have a 3rd party unlocked iPhone.

We have a trial fix for push notification on hacktivated iPhones http://bit.ly/FxBtZ . We’ll polish it up but need feedback.

Source

This app only works with the iPhone 3GS and on legit-activate iPhone 3GS.

It’s not a daemon that takes any resources, and it doesn’t add a task to your baseband. It’s very close to a true unlock. All it does is patch three files, CommCenter, lockdownd, and your wildcard activation plist(which you need, activate w at&t sim first, no hacktivation support yet).

GeoHot says his payload for this unlock is radically different and much ‘cleaner’ than other sn0w products (Ultrasn0w) out there.

He also reminds as all that this is in BETA so backup first.

Here is how to do it. Remember you need an iPhone 3GS that is Legit-activated. Don’t forget to disable 3G if you are on T-Mobile

1. Add apt.geohot.com to Cydia
2. Install com.geohot.purplesn0w
3. Watch for success output in Cydia
4. Reboot, and enjoy your unlocked iPhone

You now have an unlocked iPhone 3GS.

Do not upgrade to 3.1 yet if you want this unlock!

Here’s a brief video demonstration by @planetbeing of the iPhone Dev Team’s ultrasn0w unlock for the new iPhone 3G S. Special thanks to @Oranav for the at+xlog crash — a gift to the community that has kept on giving!

Our ultrasn0w program uses the at+xlog crash as an injection vector of our unlocking payload — and it does so on the 3GS in exactly the same way as on the 3G!  But this injection vector will be lost if you update to 3.1 using the official Apple IPSW, which updates the baseband.  So stay away from official 3.1 IPSWs until we release the tools that let you update the firmware without updating the baseband.

As I said, it is very easy to do. Here is the instruction as found on the creators website:

1. Ensure you have upgraded to iPhone OS 3.0
2. Jailbreak your iPhone 3G using redsn0w or PwnageTool (this will also install Cydia/Icy)
3. Run Cydia or Icy
4. Please add the repo repo666.ultrasn0w.com to Cydia or Icy. That last “o” is actually the number zero “0”! If you use the letter “o” you’ll get an error.
5. Search for ‘ultrasn0w’ in cydia or icy and install ultrasn0w
6. Reboot your iPhone 3G
7. T-Mobile USA users should disable 3G before using ultrasn0w
8. Enjoy

Just to clarify what this does, this allows you to use other sim cards on a locked sim card iPhone. You can use this only on the iPhone 3G and ones that are on OS 3.0.

Here is a copy of the demonstration if you missed it (start the video at 2 mins):

www.youtube.com/watch?v=kd5vOy2m5uY

More info:

• Only ultrasn0w is going to take til Friday to get pushed out.  All of our other tools should be out pretty soon after the official Apple release.
• If you apply our jailbreak when it comes out, you can install ultrasn0w anytime after that.  You obviously won’t have cell service in the meantime, though.
• This may in fact be directly applicable to the iPhone 3GS if it can be jailbroken, because it runs the same baseband version.  Whether or not it can be jailbroken is a big question right now!
• If you’re on Twitter, please give @Oranav a pat on the back.  He could have revealed the crash he found to Apple and maybe gotten quite an incentive in return. Instead, he told us about it so that we could work it into an injection vector for the soft unlock.

Source