2ND Edit: The Dev Team says the yellowsn0w Cydia package will be up as soon as the dev team member in charge of the repo fixes a file permission error. See update 3 on the dev team blog post

3rd Edit: If you do NOT have the 02.28.00 bootloader, and are going to want to unlock - do yourself a favor. Back up your stuff now, restore to a fresh 2.2 IN ITUNES, then use PwnageTool to make that a jailbroken 2.2 with 02.28.00 baseband (this guide). That way you won't have to when the unlock is released here shortly.

Now, that in binary translates to vtaber 61060174. What is that? A German blog surmises vtaber is most likely ROT13 code. EDIT: The German guys found that info from a comment on the Dev blog apparently... (hi, Germans ) In that case, the post would translate to IGNORE 61060174. Post 61060174 on the Dev Team blog said, in a nutshell, that you'd need to preserve your baseband at the 02.11.07 version (check Settings > General > About > Modem Firmware to find your baseband version) if you wanted a 3G software unlock on your iPhone.

Could the dev team be letting us know to ignore that part now? That the yellowsn0w release, coming up today, will work on the newer baseband as well?

A few hundred thousand 02.28.00 baseband users who would like to unlock their 3G iPhones sure hope so.

Update: The scamming ******bag is at it again. We DO NOT have a twitter account called ‘yellownsn0w’, and similarly no .net domain name related to yellowsn0w, don’t add this to your bookmarks. We would like you guys (currently 29 of you) to stop following him on twitter, and to also block him if he is following you. We need to see that 29 number decrease! do it people! He is a spammer! :-(

If you watched the presentation at 25C3 the dev team gave they explicitly said that the method they used couldn't be stopped by apple at this point in time. And that it would work on all current and likey all future firmwares. When they first said that the first thing that came to my mind was that post they previously made about their unlock not working on the 2.2 firmware baseband. I'm surprised nobody in the audience asked them about it at the end.

If the translation of the binary is correct, "IGNORE 61060174" then it all makes sense.

And yes, the people asking questions (mostly those not asking questions) were pretty lame. Four people from the Dev Team on stage for a Q&A and no decent questions to ask them, for shame. Wish I could have gone.

If you watched the presentation at 25C3 the dev team game they explicitly said that the method they used couldn't be stopped by apple at this point in time. And that it would work on all current and likey all future firmwares. When they first said that the first thing that came to my mind was that post they previously made about their unlock not working on the 2.2 firmware baseband. I'm surprised nobody in the audience asked them about it at the end.

If the translation of the binary is correct, "IGNORE 61060174" then it all makes sense.

That's because the firmware and the baseband are two separate pieces of software. The 3G unlock is dealing almost entirely with the baseband, so the firmware really doesn't matter, unless the baseband is upgraded along with it.

I am lucky and have been smart about this since day 1 literally. I was like the 2nd person to get one the day they came out in my town. I'm still rocking 02.08.01 firmware. I really hope it unlocks all basebands, I have friends that work with me at T-mobile that want to use their 02.22.00 baseband iPhone at work on T-mobile's network like I will be doing tomorow at work (hopefully) haha.

That's because the firmware and the baseband are two separate pieces of software. The 3G unlock is dealing almost entirely with the baseband, so the firmware really doesn't matter, unless the baseband is upgraded along with it.

I realize that but I'm pretty sure since MuscleNerd was dealing with the baseband only, when he talks about firmware he meant the software for the baseband since the firmware contains both the system software and baseband as one package. He said the code will work regardless of what new firmware comes out because it's not a bug they are exploiting for the code to work. Only thing they would have to do is find a new exploit to inject the code in. Therefore this code works on all basebands, just the deployment method will change for each particular firmware update.