As announced yesterday, Dev Team member MuscleNerd did a demo of UltraSn0w, the new software unlock for the iPhone 3G (skip to 2.20 min on the video below). Unlike its predecessor YellowSn0w, UltraSn0w will unlock your iPhone 3G no matter what firmware, bootloader or baseband you have, as long as you have the new 3.0 firmware installed.
The actual program that UltraSn0w injects into the baseband to accomplish the unlock is the exact same one the Dev Team developed for YellowSn0w. What changed is that the Dev Team found a new “hole” to inject the unlocking payload.
During his demo, MuscleNerd successfully jailbroke his iPhone 3G and proved it by inserting a T-Mobile SIM card.
UltraSn0w won’t be available until Friday and like YellowSn0w, it will be downloadable through Cydia. Your iPhone will obviously have to be jailbroken and the Dev Team will release the necessary tools for that (QuickPwn and PwnageTool) soon.
Again, just to make this clear, there is no baseband downgrade needed. You can just upgrade to 3.0 tomorrow and wait for the Dev Team to push its unlocking tools and UltraSn0w on Friday.
Note that this unlock is only valid for the iPhone 3G. According to the Dev Team, this hack may be applicable to the new iPhone 3G S if it can be jailbroken, which should happen sometimes soon. Go Dev Team!
Dev Team member MuscleNerd sent a tweet a few minutes ago about an upcoming live demo of the YellowSn0w unlock for iPhone 3.0. The live demo will happen Tuesday night, most likely on Qik and should answer a lot of questions.
This demo should show how YellowSn0w can unlock firmware 3.0. I assume this unlock will only work for iPhones that currently support YellowSn0w.
You gotta love the Dev Team! It hasn’t been 24 hours since Apple released the fifth beta of their OS 3.0 that our favorite team of iPhone hackers has already shown proofs that it has been jailbroken. And better than that, the Dev Team says that unless Apple changes the hardware of the iPhone, all future version of the OS will be jailbreakable as well.
As should be expected, the modern devteam jailbreak process is still valid. The picture below is 3.0beta5 jailbroken on an iPhone 3G. As we’ve said in previous posts, nothing other than a hardware respin can prevent our jailbreak from working on all exisiting iPhone and iPod Touches. They’ve chased our jailbreak so far down in the chain of trust, the only way they can fix it is in hardware.
One thing worries me a bit here though. Why is the Dev Team so open about it? I mean, they said several times now that Apple would have to spin the iPhone hardware to prevent all future jailbreak. If I was the Dev Team, that’s something I would keep for myself. I assume by now Apple has figured out what little piece of electronics it needs to add to the future iPhone to prevent any jailbreak.
What I think about that is that the Dev Team likes challenges. It likes to be fair play too! It’s as if the Dev Team said to Apple “hey, look what you need to do to prevent me from hacking your phone. I’m telling you all that because I’m smarter than you and whatever you do, I’ll still me able to hack your phone”.
In its blog post today, the Dev Team also warns us about the non-official version of QuickPwn:
Because there are so many beta releases, we couldn’t possible refine, test, and release both PwnageTool and QuickPwn for each of them. That’s why we’re waiting until the final release. You may have seen other “hijacked” versions of QuickPwn out there, but all of them are buggy, none of them work on OSX, and almost everyone who uses them reverts back to 2.2.1 (because none of the useful jailbroken apps (Qik, Cycorder, and others) work on 3.0 yet).
As usual, it is safe to remind everyone that if you care about the YellowSn0w unlock, you should NOT play with the 3.0 betas as they may prevent you from ever being able to unlock your iPhone.
I am currently in my home country of France for a couple of weeks. Before getting here, I was a little worried about whether I could use my iPhone with a local carrier as I never was able to try YellowSn0w when I was in the US. I unlocked my iPhone 3G about a month ago using YellowSn0w but since all my friends either are with AT&T or Verizon, I couldn’t make sure the unlocking worked.
One of the first things I did when I got at my Mom’s was popping out her Orange (French carrier) SIM and put it in my iPhone. An error message showed up saying the SIM was locked and giving me the option to unlock it. I taped “unlock” and waited a few seconds until I realized that I was not getting any cell signal at all.
I rebooted my iPhone, got the same error and still no success. Until I finally remembered that the SIM card you put in your jailbroken iPhone cannot be SIM locked. This means that the SIM card can’t be protected by a PIN.
So I put back the SIM card in my Mom’s phone and went to the settings to deactivate the lock on the SIM. As I am writing this, I realize that I probably could have deactivated it from my iPhone’s settings…
Two seconds later, I was getting signal and tried making my first call with my unlocked phone. It was a success. I also realized that I was getting on Edge. I asked my Mom if she had Internet access on her phone but she said she didn’t. I launched Safari and went online in no time. My Mom had Internet access on her phone and she wasn’t even aware of it…
The following day I went buy a my own SIM card as I couldn’t use my Mom’s for the next 2 weeks… I bought a SFR SIM as it to me the best carrier.
So this is my success story with YellowSn0w. If there is one thing to remember here, it is that if you have an issue with YellowSn0w, make sure the SIM you insert in your iPhone is not locked (PIN protected).
Since firmware 2.2.1 was released yesterday, a lot of concerns were raised whether or not you should update. The quick answer is NO, do not update if you care about your jailbreak or your unlock. MuscleNerd released a video on Qik giving us more info about the situation. Below are notes from the video.
About the iPhone 3G:
If you use YellowSn0w, you do not want to update to 2.2.1 as it will remove the possibility to install it. The only way you could do it is my installing a custom firmware that doesn’t update the baseband. PwnageTool and QuickPwn do just that but they haven’t been updated for 2.2.1 yet so wait for them to come out.
About the iPod Touch 2G:
The 2.2.1 firmware doesn’t affect your ability to jailbreak your iPod Touch 2G. It didn’t remove the ability for the Dev Team to do a tethered jailbreak. The Dev Team is still looking for an exploit to allow an untethered jailbreak. In other words, hang in there, they are working on it.
About iPhone 2G and iPod Touch 1st Gen:
2.2.1 doesn’t affect your ability to jailbreak or unlock but again, wait for an updated version of QuickPwn and PwnageTool to do that.
As usual, I will report to you as the news come about 2.2.1 and jailbreaking/unlocking so you may want to subscribe to the RSS feed to be notified in time.
If you follow the Dev Team on Twitter, you prbably saw this tweet that points to a website named www.RedSn0w.com. You can’t help but noticing how close this domain name is to YellowSn0w, the iPhone 3G soft unlock…
Looking at it a little closer and doing a “who is” search for the 2 domain names (YS – RS) show that both domains are hosted on the save servers, which makes it very likely that RedSn0w was registered by a member of the Dev Team and most importantly, that RedSn0w is a new product from our favorite Apple hackers.
It doesn’t require you to be some kind of psychic to figure out that an iPod Touch jailbreak is the only thing right now. We have the iPhone 2G and 3G jailbreak and unlock. We have the iPod Touch 1st gen jailbreak. All we need now is an iPod Touch 2nd generation jailbreak.
So what do you think? Am I right? Am I wrong? I look forward to reading your thoughts…
UPDATE: It seems I am on something here. After asking MuscleNerd, Pumpkin, and the Dev Team on Twitter to comment on my post, they all gave the same answer within minutes (see 1, 2, 3).
If there is one good thing about the Dev Team, it’s that they work fast. Following a few issues with YellowSn0w, they have already updated it to version 0.9.4 and it supposedly fixes a bunch of issues. It is still in beta but it’s much more stable than it was. So if you had issues unlocking your iPhone 3G using YellowSn0w, try again with the latest version.
It’s still available in Cydia and you can still read this for the full iPhone 3G unclok tutorial.
[digg-me]Below are instructions on how to unlock your iPhone 3G using Yellow Sn0w. Unlocking your iPhone 3G will make it possible for you to use any cellphone carrier.
Before you go any further, make sure to READ EVERY SINGLE WORD OF THIS TUTORIAL. If you think you’re too cool for school, then go directly to the instructions but please, do not complain if you mess up your iPhone during the process, which is very unlikely to happen anyways…
First things first. In order to be able for you to use Yellow Sn0w to unlock your iPhone 3G, you have to be on a jailbroken iPhone that runs the latest firmware 2.2 with the latest baseband 02.28.00. To find out what firmware you’re on, go to Settings > General > About and look for “Modem Firmware”. It should say 02.28.00.
If you have not jailbroken your iPhone yet, you have to now in order to unlock. To jailbreak your iPhone, follow the QuickPwn 2.2 guide that I wrote a few weeks ago.
If you have already jailbroken your iPhone using PwnageTool to preserve your baseband, sorry but you have to restore and rejailbreak again in order to have the latest 02.28.00 baseband.
If you have updated to the latest firmware 2.2 with its latest 02.28.00 baseband, then you’re good to go.
So from now on, I assume that you are on a clean firmware 2.2 with firmware 02.28.00 and that your iPhone is jailbroken.
1. Go to Cydia and install this new source: http://apt9.yellowsn0w.com/ (note that snow is spelled with a zero, not an “o”). To install a new source in Cydia, go to Manage > Sources > Edit > Add, then type in the source http://apt9.yellowsn0w.com/ and tap “Add Source”.
2. Once the source has been added, tap “Return To Cydia”, then tap “Done”.
3. Now tap “apt9.yellowsn0w.com from the list of sources “Entered By Users”.
4. Select Yellow Sn0w, then tap install nad confirm.
5. Once the installation had been successfully completed, return to Cydia.
6. Hard reset your iPhone. To do this, hold the home and power buttons simultaneously for a few seconds until the phone shuts off by itself (ignore the “slide to power off” message)
7. Insert whatever SIM card you want! Wait a few seconds and you should be good.
See, that wasn’t too hard at all. Users that are already familiar with Cydia and sources shouldn’t have any problem at all. But first time jailbreakers might be a little lost, which is why I detailed this tutorial a lot.
Now there are a few known issues with Yellow Sn0w and I highly recommend you either read my previous post about it, or go directly to the Dev Team’s blog.
1) If you are on tmobile USA you should disable 3G in Settings or sbsettings.
2) YellowSn0w does not work with a SIM PIN. You must disable your SIM card pin lock.
At any rate, I would really appreciate it if you could digg this post, then write a comment, then go to the Dev Team’s blog to thank them for their great work.
Mobile Crunch published a nice interview with Pytey, one of the preeminent Dev Team members. Interviews with Dev Team members are very rare and I suggest that you have a look at it if you’re remotely interested in jailbreaking and unlocking your iPhone. The interview obviously evolves a lot around the awaited Yellow Sn0w, supposed to be available today.
Here is my favorite part of the interview:
However, Apple places restrictions on what you can run on the device. They impose draconian restrictions on the type of application that you can run, they don’t allow applications to run in the background and they even restrict the applications by subject matter or if they compete with their own applications. If I buy a device I want to be able to do what I want with it, if that involves gambling or looking at an application that involves porn then so be it. The real estate agent who sold me my house doesn’t knock on my door every month to check what pictures I have hanging on the walls, so why should Apple have this right?
Earlier this month, I published a translation of another interview with Pytey.
Earlier today, the Dev Team published a post on the blog with some strange binary codes that won’t mean anything to anyone that doesn’t speak geek fluently (I don’t!). I completely disregarded this post as I thought it was a pre-message for tonight’s release of yellow sn0w, the new unlocking tool that will be available sometimes today through Cydia.
However, a tweet from twitter user Yellow Sn0w got me all excited when it said that it will be safe to use yellow sn0w on any firmware. Tweeting back and forth with him, I was directed to a blog post of his that actually explains the full meaning of the binary codes posted by the Dev Team.
Here is his explanation:
In binary that message translates to vtaber 61060174. vtaber translates to “ignore” and the 61060174 means post# 61060174 on the iPhone DevTeam blog. http://blog.iphone-dev.org/post/61060174/the-man-from-delmonte-he-say-yes
Hoping that this is true…