Zune Unbricks Self

Who said they weren't?
They already issued a statement YESTERDAY saying it would be fixed by the next leap year. They know what the issue is, and they know how to fix it. They've got 4 freaking years to do so.

It was a comment on what they need to do. For someone that presumably doesn't work for MIcrosoft, you're incredibly oversensitive to any comments that aren't completely pro-MS.

Like Apple bricking their products via updates?
Or shipping Viruses with the iPods?

Completely different. Bricking occured on hacked iphones. The Viruses were introduced at the factory and were not a part of the software.

This was a mistake in a basic library. You don't write a new Time/Date library and forget to test if it works leap year. I'm not MS basher, but basic unit testing should have caught an error in calculating leap year.

Mistakes happen, but Time/Date libraries are well known problems that ahve been solved in C, C#, Java, Perl, C++, VB and every other language that MS would have coded the software in.

It's not the end of the world, it's not the same as a virus...they can't test their iPod software for a virus that isn't in the software.

And they put out warnings stating that applying certain IPhon Updates might cuase the jail broken iphones to stop working.

Are you going to say that MS should be responsible for problems in versions of Windows that are hacked to do things it was not intended to do? Of course not. S/W houses support the software they wrote.
 
It was a comment on what they need to do. For someone that presumably doesn't work for MIcrosoft, you're incredibly oversensitive to any comments that aren't completely pro-MS.



Completely different. Bricking occured on hacked iphones. The Viruses were introduced at the factory and were not a part of the software.

This was a mistake in a basic library. You don't write a new Time/Date library and forget to test if it works leap year. I'm not MS basher, but basic unit testing should have caught an error in calculating leap year.

Mistakes happen, but Time/Date libraries are well known problems that ahve been solved in C, C#, Java, Perl, C++, VB and every other language that MS would have coded the software in.

It's not the end of the world, it's not the same as a virus...they can't test their iPod software for a virus that isn't in the software.

And they put out warnings stating that applying certain IPhon Updates might cuase the jail broken iphones to stop working.

Are you going to say that MS should be responsible for problems in versions of Windows that are hacked to do things it was not intended to do? Of course not. S/W houses support the software they wrote.

Actually though in this case was it really Microsoft at fault? It only happen with the 30GB zune as they have a differnet chipset than the others. So to me that sounds more like the fault of the chipset & its firmware than an "OS" issue on the zune. The fact that every other zune worked just fine shows that Microsoft did make working time/date code. But whom ever made the chipset and the code to control it didn't ever think that there were more than 365 days in a year.

In that regards, yes they should have maybe tested them a little bit better. However I understand why they never. They made the code to work just fine. It worked fine on most platforms other than one. That would be like Windows having an issue with the date / time if you are running 1 single chipset on 1 motherboard product line. Short of testing every single hardware & software combination in full to make sure nothing like this happens you are bound to have something slip through the cracks.
 
Actually though in this case was it really Microsoft at fault? It only happen with the 30GB zune as they have a differnet chipset than the others. So to me that sounds more like the fault of the chipset & its firmware than an "OS" issue....

In that regards, yes they should have maybe tested them a little bit better. However I understand why they never. They made the code to work just fine. It worked fine on most platforms other than one. That would be like Windows having an issue with the date / time if you are running 1 single chipset on 1 motherboard product line. Short of testing every single hardware & software combination in full to make sure nothing like this happens you are bound to have something slip through the cracks.

They had to test every single chipset combo for the Zune. That is one entire chipset. Are you really telling me that MS could not test a SINGLE chipset? It's not like they released the Zune "OS" and everyone and their mom jumped on-board creating their own chips to run this software. No, MS chose the chipset, wrote the software, and utterly failed to test an incredibly basic issue.

MS = fail. You = fail.
 
They had to test every single chipset combo for the Zune. That is one entire chipset. Are you really telling me that MS could not test a SINGLE chipset? It's not like they released the Zune "OS" and everyone and their mom jumped on-board creating their own chips to run this software. No, MS chose the chipset, wrote the software, and utterly failed to test an incredibly basic issue.

MS = fail. You = fail.


hes saying that a single part found only on the 30gig zunes were at fault, and the others worked fine. Im a little sick of people like you being asses around here.
 
That's exactly what I'm saying. They had to test for a single part, not for endless combos of chips. :rolleyes:
 
i have a 30 gig zune ver 1.0 the one with the round button instead of the square one at the bottom, and it will not reset itself. i think thats what the difference is in people saying it resets or it wont. i know there are 2 versions, the one with the square menu button thats out now, or the one with the round menu button out that was out about a year or so ago that i have. the one i have has a left arrow button, a right arrow button/pause button and the large round up/down/left/right menu button with a smaller round button in the middle of it.

anyway, when you press the play/pause button, you get a battery with a ! in the middle of it for about 3 seconds, then it goes off screen. there is no way to keep it on screen to run down the battery even.

does anyone know microsofts number to call for support as i really think they overlooked the version 1.0 when they magicly fixed the issue. i want to call them and give them a peice of my mind.
 
It was a comment on what they need to do. For someone that presumably doesn't work for MIcrosoft, you're incredibly oversensitive to any comments that aren't completely pro-MS.
Even though I'm blaming this squarely on Microsoft? :rolleyes:

The comment was that they would be too incompetent or something to bother fixing this. They've got 4 years to do that, is my point.


Completely different. Bricking occured on hacked iphones.
It was UNLOCKED phones. Not like they were cracked activation or something else, they were simply unlocked.
And considering how fast (Well, at least for Apple) they turned around and issued a patch for it: it wasn't intended to happen.



The Viruses were introduced at the factory and were not a part of the software.
So, Apple's QA department can let stuff slide like that, but Microsoft can't? :rolleyes:
This is exactly why I jump onto people bashing Microsoft all the time. It was "cool" 10 years ago.

Actually though in this case was it really Microsoft at fault?
Like I've said before... YES.
It was not the chipset itself, it was the driver. IE, a piece of software.
 
lol my high horse? okay. If you were designing a time/calendar program, would the concept of a "leap year" really not cross your mind? Isn't that one of the fundamental concepts behind how our calendar system works? I guess I'm just stumped as to why something that simple could escape an entire design team. But apparently that makes me elitist?

You know, whenever Apple has a problem like this everyone on this forum freaks out and cites how much apple sucks, but curiously when MS has a similar issue everyone says "no it's cool it's just a small mistake." Shouldn't we hold both companies to equal standards?

Holy crap, the voice of reason.

1000% agreed. Apple were rightfully thrown under the bus with their awful 2.0 firmware for the iPhone. It was fixed with the next update but it was obviously not ready for primetime when it did go out last July. Ditto MobileMe which went out at the same time, a disaster at launch. And MS is somehow given a pass when stuff like this happens, or when they try to patent ridiculous things like pay-as-you-go computing (which was thankfully shot down), or when they have a great product like the 360 that unfortunately has the absolute worst hardware failure rate of any piece of consumer electronics that I can remember. I guarantee you that the vitriol here would be ridiculous (and ironically correct!) if the same thing happened with an Apple product.

Any company should be criticized and called out for what they do wrong, but the hypocrisy you see around here as far as giving out free passes based on fanboyism is pretty crazy sometimes.
 
It was a comment on what they need to do. For someone that presumably doesn't work for MIcrosoft, you're incredibly oversensitive to any comments that aren't completely pro-MS.

He's the equivalent of the rabid Apple fanboy on a Mac forum or a Linux zealot on Slashdot. You should be used to this by now. :eek:
 
Who here did not resist the urge to open their in-warranty Zune and fix the problem themselves?


I'm sure there were some dumb asses that did just that. :rolleyes:

I look for Microsoft to have an upcoming firmware update that will keep this from happening again in 4 years. My daughters' bricked yesterday and she was freaking a little until I fired up my computer and saw it was widespread with everyone with a 30gb Zune had the same problem. I told her to not sweat it that it would probably fix itself if she ran the battery down completely so it would re-set itself and wait until today to crank it back up. She thinks I'm a uber geek god (almost) now. ;)
 
after leaving mine plugged in for 3 hours, mine reset itself. i didnt have to press anything on the player itself. so im ok its fixed at least. ms are a bunch of asses though, im sure thousands of people tossed them in the trash, or are going to resell them as broken, in the months to come.
 
Who here did not resist the urge to open their in-warranty Zune and fix the problem themselves?

i opened mine and unplugged the battery, it's both out of warranty and i've opened it before... i think i'm fucked either way... fuck
 
They had to test every single chipset combo for the Zune. That is one entire chipset. Are you really telling me that MS could not test a SINGLE chipset? It's not like they released the Zune "OS" and everyone and their mom jumped on-board creating their own chips to run this software. No, MS chose the chipset, wrote the software, and utterly failed to test an incredibly basic issue.

MS = fail. You = fail.

Yes, it's Microsoft's job to be sure that every component they test is bug-free. :rolleyes::rolleyes:

You MS bashers are getting sad. Are you honestly under the delusion that it's their job to do that? Do you actually think ANYTHING would get done in this world if every business hired a QA team to test every part? Moreso, do you think brandname would mean jack-shit if every single item ever produced was being tested by thousands of QA teams around the world? The entire point of a brand-name is to assure those using your product that it meets the specs that you say it does.

You should probably just stop. You're starting to sound pretty sad.
 
i found this on the zune.net forums

Hopefully I am not repeating exactly what someone else said, but I didn't feel like reading every post.



Mine wasn't working with all the steps listed in different threads. Here are the steps I followed and it is finally recognizing and syncing:



1. Even if you have done a hard reset with no results, plug in your Zune to charge. I did it on my laptop.

2. After about 5 to 10 minutes of charging, remove the cable.

3. Hit the play button and as soon as the Zune screen appears hit the Back-Left-Center button.

4. Once it starts the hard reset, plug it back into the computer.

5. Your computer should recognize the Zune and start installing. Your Zune will then say "On your PC, open the Zune software and restore the Zune device firmware". Follow those steps.



It seems to take quite a bit of time and lots of loading and reloading on the Zune, but it syncing!!!! I will update if it freezes after syncing.



I am definitely not guaranteeing this will work for everyone, but it seems to be working for me and maybe it will work for some of you.



UPDATE: It appears to be working. It synced all my music and I let it charge a bit longer. I played just fine. I shut it off, plugged it again to charge, and it is charging just fine.

i'm trying this now
 
Actually though in this case was it really Microsoft at fault? It only happen with the 30GB zune as they have a differnet chipset than the others. So to me that sounds more like the fault of the chipset & its firmware than an "OS" issue on the zune. The fact that every other zune worked just fine shows that Microsoft did make working time/date code. But whom ever made the chipset and the code to control it didn't ever think that there were more than 365 days in a year.

In that regards, yes they should have maybe tested them a little bit better. However I understand why they never. They made the code to work just fine. It worked fine on most platforms other than one. That would be like Windows having an issue with the date / time if you are running 1 single chipset on 1 motherboard product line. Short of testing every single hardware & software combination in full to make sure nothing like this happens you are bound to have something slip through the cracks.

That i don't know, but generally speaking, time on all systems is given in seconds (or is it milliseconds) since 1/1/1970 GMT. It's up to the software to determine what that number means. I suppose it's possible that that function is in the chipset.

If that is, in fact, the case, then I take back my criticism of MS's testing.
 
They had to test every single chipset combo for the Zune. That is one entire chipset. Are you really telling me that MS could not test a SINGLE chipset? It's not like they released the Zune "OS" and everyone and their mom jumped on-board creating their own chips to run this software. No, MS chose the chipset, wrote the software, and utterly failed to test an incredibly basic issue.

MS = fail. You = fail.

Do you think that Java or C++ programmers exhaustively test every standard library to make sure they function correctly in every single scenario? Maybe you would if you were writing software for a nuclear reactor (they probably do), but for a DAP, you probably don't.

As I said earlier, this is such a basic well known problem, one could reasonably expect that the provider of that library/service to have tested it.

That said, I'm still not convinced that this isn't something MS wrote incorrectly. I'd expect the chipset to give the number of seconds since 1970, and nothing else.
 
That i don't know, but generally speaking, time on all systems is given in seconds (or is it milliseconds) since 1/1/1970 GMT. It's up to the software to determine what that number means. I suppose it's possible that that function is in the chipset.

I would probably expect the device to use Julian dates. IE, 2008365 would have normally been the last day. However when day 2008366 hit it got screwed up.

And Microsoft still said this was a DRIVER. Unless they said it was a hardware malfunction or an actual chipset problem, driver means a little piece of software.

Still Microsoft's fault, but like others have said you can't think of EVERYTHING, that's why every piece of software on earth has updates.
 
Yes, it's Microsoft's job to be sure that every component they test is bug-free. :rolleyes::rolleyes:

You MS bashers are getting sad. Are you honestly under the delusion that it's their job to do that? Do you actually think ANYTHING would get done in this world if every business hired a QA team to test every part? Moreso, do you think brandname would mean jack-shit if every single item ever produced was being tested by thousands of QA teams around the world? The entire point of a brand-name is to assure those using your product that it meets the specs that you say it does.

You should probably just stop. You're starting to sound pretty sad.

Of course it's there job. The key to writing good software is exhaustively test everything in the underlying OS/Programming Libraries and so on.. After you've done that, then you can start working on your software.

Yes it adds years to the development time, costs millions of dollars and yes, you're effectively testing what you should rightfully assume that the developer of that product should have tested, but that's what we're supposed to do..... <sarcasm/>

I hope it was the chipset that's at fault (though I have serious doubts), because I'd like to think MS wouldn't let basic testing of their own code get past developer unit testing, much less QA.
 
Do you think that Java or C++ programmers exhaustively test every standard library to make sure they function correctly in every single scenario? Maybe you would if you were writing software for a nuclear reactor (they probably do), but for a DAP, you probably don't.

As I said earlier, this is such a basic well known problem, one could reasonably expect that the provider of that library/service to have tested it.

That said, I'm still not convinced that this isn't something MS wrote incorrectly. I'd expect the chipset to give the number of seconds since 1970, and nothing else.

http://www.engadget.com/2009/01/03/y28-zune-quirk-really-a-freescale-bug/

Toshibas Gigabeat unit, same problem (but basically the same unit as the Zune)

And this
http://en.wikipedia.org/wiki/Gigabeat
"Although Microsoft's Zune is based on the hardware of this player"
refering to the Gigabeat "S" unit.

If anything the Zune 30 design was bought from Toshiba. That would mean Toshiba dropped the ball, and Microsoft didn't catch it either.
 
http://www.engadget.com/2009/01/03/y28-zune-quirk-really-a-freescale-bug/

Toshibas Gigabeat unit, same problem (but basically the same unit as the Zune)

And this
http://en.wikipedia.org/wiki/Gigabeat
"Although Microsoft's Zune is based on the hardware of this player"
refering to the Gigabeat "S" unit.

If anything the Zune 30 design was bought from Toshiba. That would mean Toshiba dropped the ball, and Microsoft didn't catch it either.

Then I cast blame on the Freescale or whoever wrote the drivers/API that interact with that H/W.

In an ideal world, MS would have tested it, but my guess is part of the reason they based it on Toshiba's unit was to decrease their TTM on the 1G Zune.

Anyway you look at it, this is no longer MS not testing their code. This is, apparently, Freescale not testing their drivers, Toshiba not testing validating the drivers and Ms not validating the drivers that the other 2 didn't validate.

All in all, I'll give MS a pass on this one, so long as the patch is released in less than 1458 days.
 
i have a 30 gig zune ver 1.0 the one with the round button instead of the square one at the bottom, and it will not reset itself. i think thats what the difference is in people saying it resets or it wont. i know there are 2 versions, the one with the square menu button thats out now, or the one with the round menu button out that was out about a year or so ago that i have. the one i have has a left arrow button, a right arrow button/pause button and the large round up/down/left/right menu button with a smaller round button in the middle of it.

anyway, when you press the play/pause button, you get a battery with a ! in the middle of it for about 3 seconds, then it goes off screen. there is no way to keep it on screen to run down the battery even.

does anyone know microsofts number to call for support as i really think they overlooked the version 1.0 when they magicly fixed the issue. i want to call them and give them a peice of my mind.


im not sure how to help, but if im correct, all 30gig zunes have the circle button, not the square "touchpad"
 
i have a 30 gig zune ver 1.0 the one with the round button instead of the square one at the bottom, and it will not reset itself. i think thats what the difference is in people saying it resets or it wont. i know there are 2 versions, the one with the square menu button thats out now, or the one with the round menu button out that was out about a year or so ago that i have. the one i have has a left arrow button, a right arrow button/pause button and the large round up/down/left/right menu button with a smaller round button in the middle of it.

anyway, when you press the play/pause button, you get a battery with a ! in the middle of it for about 3 seconds, then it goes off screen. there is no way to keep it on screen to run down the battery even.

does anyone know microsofts number to call for support as i really think they overlooked the version 1.0 when they magicly fixed the issue. i want to call them and give them a peice of my mind.

It sounds like your battery is already dead. The battery symbol and the ! means the battery is dead. Connect the Zune to the usb plug to charge it. It will need to charge for a few minutes before it will turn on. The battery symbol and the ! will display during this time. After a few minutes of charging it should cut on by itself. When it does turn on and starts to boot you will see the Zune logo and a bar at the bottom. The bar should fill from left to right. It the bar hangs in this process than your Zune is still bricked.
 
It sounds like your battery is already dead. The battery symbol and the ! means the battery is dead. Connect the Zune to the usb plug to charge it. It will need to charge for a few minutes before it will turn on. The battery symbol and the ! will display during this time. After a few minutes of charging it should cut on by itself. When it does turn on and starts to boot you will see the Zune logo and a bar at the bottom. The bar should fill from left to right. It the bar hangs in this process than your Zune is still bricked.

what he said except when you plug the usb cord in it shows the battery with a power plug logo, not a ! :p and yeah soon as it has enough juice to turn on, it will. usually takes about 5-10 minutes in my experience.
 
Back
Top