Hasta La Gadget!

The iPhone 3G unlock is now available. The unlocking software is called yellowsn0w, runs as an invisible application, and it’s very easy to install. Here’s how. Updated 3: Now works for me with 0.9.4.

Yellowsn0w, the iPhone 3G unlock, runs as a small command line application that gets installed in any jailbroken iPhone 3G using Installer. It’s very easy to install:

• First, update your iPhone 3G to the latest iPhone OS provided by Apple using the latest iTunes.

• Then, use QuickPwn 2.2 to jailbreak and activate your iPhone 3G. If you have Mac OS X 10.5.6 installed, you should follow these instructions before doing it.

• Use Installer or Cydia to install yellowsn0w, which is completely free. Here are the addresses you have to use to add yellowsn0w to your installer application:

For Cydia enter: http://apt9.yellowsn0w.com/
For Installer enter: http://i.yellowsn0w.com/

• That’s it. There are some special SIM cards that give problems, but f you have a normal SIM card from any non-official carrier, you are fine.

BEWARE: This is a beta application—version 0.9.1— so install at your own risk—I’m installing, it, though. Since it’s a daemon which doesn’t alter anything permanently, it seems safe. Just proceed with caution and be warned.

Update: I’ve been trying to get this to run all day. The installation is very easy. Getting it to work right is a completely different matter.

After reboot, the iPhone won’t pick my Vodafone carrier (the Vodafone SIM card works fine in an iPhone first generation, unlocked with the old unlock). It will just sit there, idle. Won’t give any error, but it won’t connect to the carrier network.

My iPhone 3G has the 2.28 baseband, as it should, and has been Quickpwned for the first time to do the unlock. Installer and Cydia are there, working fine. I’ve carefully followed the instructions in their page—about getting out the SIM card for a minute, then get it back in (and all other possible combinations)—but it just won’t fly.

Like they say, this is beta. It won’t damage your iPhone—in theory—but it may or may not run. It seems like there are other reports of the same, as well as other people talking about losing the network connection.

Even while this is labeled as a beta, it saddens me that the iPhone Dev Team has embraced the damn beta culture just to make the release on a cute date. It looks like the old days of solid versions are long gone by.

Update 2: There’s a poll here with people saying if it works or not. At the time of this writing, these were the stats:

It worked: 23 34.33%
It doesn’t work: 44 65.67%
Voters: 67.

Hopefully, a more stable and predictable release will come soon. Until then, I will keep trying. If you have any reports, drop me a line via email.

Update 3: iPhone Dev Team has released version 0.9.4. After some magic moves in the terminal, it worked for me. My iPhone 3G is now working in Spain in the Vodafone network. [IPhone Dev Team]

Bricks! Minifigs! Spaceships! Star Wars! Airplanes! Robots! Sex! Secret Vaults! Our exclusive trip to the Lego mothership! More than six million read the best Lego stories of 2008. Check the Top 10 and my favorites.

Most Popular Lego Stories of 2008

1. The Lego Secret Vault
459,413 views, my favorite Lego story of the year by far.
Video exclusive

2. 3,800-Piece Death Star Diorama Is Coolest Star Wars Set Ever
249,263 views

3. Best Lego Sets In History
245,771 views
Exclusive

4. Lego Brick Timeline: 50 Years of Building Frenzy and Curiosities
217,115 views
Exclusive

5. Lego Master Completes 30-Pound Star Wars Starship
183,202 views

6. Inside the Lego Factory
167,815 views
Video exclusive

7. Lego Airbus A380 Is Biggest Lego Airplane In the World
151,317 views
Video exclusive

8. Forbidden Set Shows Darkest Side of Lego
137,344 views

9. Lego Colonial Space Ship Is Big Enough to Terraform Real Planets
137,268 views

10. Using Hundreds of Lego Star Wars Mini Spaceships to Create Huge Battles
135,898 views

Some of my favorites

65-Foot-High Lego Cathedrals Store 19 Billion Pieces a Year
This thing amazes me every time I see it.
Video exclusive

The Lego Minifig Timeline
135,089 views
Exclusive

How Lego Builds the Minifig
Video exclusive

750,000-Piece Lego Kennedy Space Center Is the Mother of All Lego Models
Video exclusive

Winners of the Go Miniman Lego Video Contest
I still can’t believe our readers did all this. Simply stunning.

[All Lego stories at Giz]

Microsoft’s responded to the Zune 30GB failure, blaming a leap-year handling bug. And they’ve provided a fix. Which is to wait til New Years, when the bug will go away by itself. Huh.

Early this morning we were alerted by our customers that there was a widespread issue affecting our 2006 model Zune 30GB devices (a large number of which are still actively being used). The technical team jumped on the problem immediately and isolated the issue: a bug in the internal clock driver related to the way the device handles a leap year. That being the case, the issue should be resolved over the next 24 hours as the time change moves to January 1, 2009. We expect the internal clock on the Zune 30GB devices will automatically reset tomorrow (noon, GMT). By tomorrow you should allow the battery to fully run out of power before the unit can restart successfully then simply ensure that your device is recharged, then turn it back on. If you’re a Zune Pass subscriber, you may need to sync your device with your PC to refresh the rights to the subscription content you have downloaded to your device.

Customers can continue to stay informed via the support page on zune.net (zune.net/support).

We know this has been a big inconvenience to our customers and we are sorry for that, and want to thank them for their patience.

Q: Why is this issue isolated to the Zune 30 device?
It is a bug in a driver for a part that is only used in the Zune 30 device.

Q: What fixes or patches are you putting in place to resolve this situation?
This situation should remedy itself over the next 24 hours as the time flips to January 1st.

Q: What’s the timeline on a fix?
The issue Zune 30GB customers are experiencing today will self resolve as time changes to January 1.

Q: Why did this occur at precisely 12:01 a.m. on December 31, 2008?
There is a bug in the internal clock driver causing the 30GB device to improperly handle the last day of a leap year.

Q: What is Zune doing to fix this issue?
The issue should resolve itself.

Q: Are you sure that this won’t happen to all 80, 120 or other flash devices?
This issue is related to a part that is only used in Zune 30 devices.

Q: How many 30GB Zune devices are affected? How many Zune 30GB devices were sold?
All 30GB devices are potentially affected.

Right, so this is a weird one: we’re getting tons of reports—tons—about failing Zune 30s. Apparently, the players began freezing at about midnight last night, becoming totally unresponsive and practically useless. Update: The easy official fix here.

The crisis has been dubbed by Zune users ‘Z2K9’, due to the apparently synchronized faceplantings across the country. According to tipster Michael, the Zune users experienced something like this:

Apparently, around 2:00 AM today, the Zune models either reset, or were already off. Upon when turning on, the thing loads up and… freezes with a full loading bar (as pictured above). I thought my brother was the only one with it, but then it happened to my Zune. Then I checked out the forums and it seems everyone with a 30GB HDD model has had this happen to them

This report is consistently corroborated by literally hundreds of others across the various Zune support and fan forums.

What hasn’t emerged yet, largely due to the fact that MS’s support lines aren’t yet open for the day, is why these devices are failing. The evidence seems to point to a software glitch, but simple resets aren’t providing any relief. Some reports indicate that only Zunes with the latest firmware are affected, but this hasn’t yet been confirmed.

The proximity of the events to the New Year, which inspired the Y2K9 moniker, provides little more than a colorful backdrop; it’s unlikely that the switching of years in the Zune’s internal calendar has anything to do with the failures (besides, it hasn’t even happened yet).

If not for the uniform representation of events across the internet, I’d be tempted to suspect this as a hoax, but it just doesn’t look that way. The story, assuming the described problem is of the magnitude reported, will probably take a turn for the large when the majority of Zuners start waking up. Let us know about your experiences in the comments. [Zunescene, ZuneBoards, Zune.net—Thanks, Michael, Josh, Ben and others]

Update: We’ve got a DIY fix to revive slain Zunes.

Update: Reader Bill Bradski (Bill Brasky?) has summed up the situation thusly:

Update 2: Here’s Microsoft’s official response for the time being (it’s clear they just woke up and probably haven’t even flipped on their coffee pots yet):

We are aware that customers with the Zune 30GB are experiencing issues with their Zune device. We are actively working now to isolate the issue and develop a solution to address it. We will keep customers informed on next steps via the support page on zune.net (zune.net/support).

According to a previously reliable source, Apple misrepresented the reasons behind Macworld and Jobs’ keynote cancellation. Allegedly, the real cause is his rapidly declining health. In fact, it may be even worse than we imagined:

Steves health is rapidly declining. Apple is choosing to remove the hype factor strategically vs letting the hype destroy apple when the inevitable news comes later this spring.

This strategic loss will be less of a bang with investors. This is why Macworld is a no-go anymore. No more Steve means no more hype. Saying they are no longer needing [Macworld] is the cover designed by the worldwide “loyalty” department.

This source has repeatedly been 100% correct before. Those times, however, were always related to news and images of unreleased Apple products. I can only hope that, in this more personal matter, it is absolutely wrong. And that if he is not, that sentence just means that Steve Jobs is retiring according to his plan.

While Steve Jobs’ health is nobody’s business—not the press, not investors, not the public—we believe that there’s a line between saying “no-comment” and plainly misleading—once again—the public.

Steve Jobs have been giving Macworld Expo keynotes since he came back as interim CEO of the company in 1997. Since then he has never failed once, always introducing notable products both at Macworld San Francisco and Macworld New York. During his latest Macworld keynote, in 2008, he introduced the MacBook Air. Later this year, he used his WWDC presentation to announce the new iPhone 3G. In his last two show-n-tells, for the new iPods and the new MacBooks, he used less time on stage, giving more limelight to key members of Apple’s executive team.

According to our Deep Throat’s report, the fact seems to be that whether or not Apple had other reasons to pull out of Macworld, they weren’t the only ones, and they certainly weren’t the same ones used for not putting Steve Jobs through the ordeal of a two-hour presentation.

Apple did not comment on this story after being contacted.