How to temporarily fix the Zune 30’s Z2K9 woes.
Since my warranty was already void as of 12/07, and because I already swapped the 30GB HDD for a 60GB HDD, I ended up opening the Zune, then reseating the cable from the battery to the main board which resets the Zune (it’s the little brown plastic piece on the right in the attached photo, the one with the long cable going to it over the hard drive).
It seems as long as the Zune isn’t sync’d again with the software open it should function. I’m still in the process of testing this but I’m guessing jumping the clock forward to Jan 1, 2009 may let things pass over fine. But then again I don’t really suggest doing this after you get it working
.
Of course, I don’t suggest voiding the warranty by opening up your Zune either. Hopefully you won’t.
UPDATE: Now that we’re in good old 2009 the Zune has righted itself thanks to the infinite loop ending. All is right in the world and the final FAQ regarding the Zune resurrection has been posted on the proper Zune support site.
UPDATE: Gizmodo posting first on the reseat fix though I don’t believe you need to unplug the hard drive so I advise against that. I also suggest waiting for the official solution to come from Zune support.
UPDATE: From the Zune forums:
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. 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.
UPDATE: Over at ZuneBoards.com, a moderator has posted up the source and analysis for the cause of the bug on the Zune 30’s. Pretty interesting. In the end a minor mistake and a missed test case causing a major headache. Likely a simple firmware update will prevent the problem again next leap year. Granted I doubt any Zune 30’s will even be able to hold a charge by then:
year = ORIGINYEAR; /* = 1980 */
while (days > 365)
{
if (IsLeapYear(year))
{
if (days > 366)
{
days -= 366;
year += 1;
}
}
else
{
days -= 365;
year += 1;
}
}

