Topic: 2858 to 1888 Kernel 'Downgrade' Confirmed, not working with 4552+ (Read 429 times)

litium33 · « **Reply #15 on:** January 23, 2007, 12:03:00 PM »

I think this news is very interesting and it's worthwile to keep the 360 not updated at the moment waiting to see what it will turn out to be.

As soon as I read the news I went to check my 360 ad found out that it mine is now a 4548 so not yet 4552.

My question is: Is it sure that the first version burning the efuses is the 4552 or just the others 45** have not been checked?

forzadude2 · « **Reply #16 on:** January 24, 2007, 12:01:00 AM »

QUOTE(dom0012 @ Jan 23 2007, 09:14 AM)

why is this posted? this isnt really breaking news in my opinion...

I find it very interesting, this is the kind of news I like! Thanks

openxdkman · « **Reply #17 on:** January 24, 2007, 01:05:00 AM »

Guys, we need a list of patches (for those not connecting to XBL and still getting some through retail games)
by retail game (or release date?), and with an idea of the efuse they blow away...

Also, theoretically... Can a lawsuit be filled since blowing up a CPU part can be considered a damage?

cpi · « **Reply #18 on:** January 24, 2007, 06:16:00 AM »

QUOTE(openxdkman @ Jan 24 2007, 08:36 AM)

Also, theoretically... Can a lawsuit be filled since blowing up a CPU part can be considered a damage?

Interesting, Since MS didn't notify the owners of the equipment that they were about to alter/damage their hardware.

Has anyone checked the EULA?

I know someone will compare this to satellite receivers but that is very different. You own the receiver and the smart card that gets modified is owned by the service provider.

cpi

echto · « **Reply #19 on:** January 27, 2007, 11:00:00 AM »

QUOTE(brywalker @ Jan 23 2007, 06:28 AM)

Wow. That DEFINITELY gives us more insight to the update = 3 red rings situation that they are addressing now.

Looks like what is happening is either:

A) During the update the EFuse doesn't blow and the dash updates fine which when checked by Hypervisor returns a no boot condition

During the update the EFuse blows correctly and the update DOES NOT flash correctly which when checked by the Hypervisor returns a no boot condition.

Very facinating.

I've been wondering about the legality of EFuses. There was nothing printed on the box or in the owner's manual stating that physical changes will be made to the product after purchasing. As far as I'm concerned the product is no longer the product I originally purchased. I'm not licensing the hardware. I flat out own the hardware and modifications took place to the hardware without notification or consent. Notification and consent only pertained to a stated software update, not a hardware update.

openxdkman · « **Reply #20 on:** January 30, 2007, 05:14:00 AM »

Please post any firmware version change occuring after a retail game launch (i.e efuses casualties).

It seems that Lost Planet and Gears of Wars, quite recent, let's say december 2006, are not pushing firmware version beyond v2858 (I guess no efuses got killed so far. Or am I wrong?)

JenovaXP · « **Reply #21 on:** March 05, 2007, 07:30:00 AM »

hey guys i'm gonna phone a lawyer today. and see if we have a case cause i looked all over the ms website and checked the eula for the 360 and live service and all it says in a nutshell is that m$ can upgrade the SOFTWARE of our consoles without prior notice. i'll reply back when i find out more

Millenia1x · « **Reply #22 on:** March 05, 2007, 01:42:00 PM »

i'm a law student and i can tell you straight out that its a good case

it depends on how much you push it

but its not a good idea to piss microsoft off

This post has been edited by Millenia1x: Mar 5 2007, 09:43 PM

echto · « **Reply #23 on:** March 08, 2007, 06:30:00 PM »

The words Class Action comes to mind.

Can someone say "Sony Root Kit"? Heres a scenario. What if silently blowing an eFuse enabled a small microphone or a cmos imaging chip behind the plastic cover of the IR LED on the front of the machine. You can build pretty much anything on silicon in this day and age. How would you like someone listening or watching you all the time without you knowing at your hardware and broadband expense?

Allowing someone to physically manipulate a product after that someone has sold the product implies that someone still has control over the product, a control that should have been relinquished at the time of sale. How about 10 millions controls that should have been relinquished.

I know. I'm going to build a condominium building and in the bathrooms install cameras behind two way mirrors. I'm going to sell the condos and at a later date take take control of the buyer's privacy without them knowing.

Math1 · « **Reply #24 on:** March 12, 2007, 05:15:00 PM »

Yea - good luck with that.

Wolves · « **Reply #25 on:** March 15, 2007, 06:15:00 AM »

Hmm, this is getting more and more interesting...

Perhaps we could force MS to take back our 360's and provide us with new consoles with unburnt efuses

Though, I'm sitting on top of a 4548, this could make a lot of other people happy.

Damn would that ever be a slap in MS's face.

Though... we're all bitching at the people who provided this with this wonderful console.

torne · « **Reply #26 on:** March 16, 2007, 04:29:00 AM »

QUOTE(Wolves @ Mar 15 2007, 12:22 PM)

Though... we're all bitching at the people who provided this with this wonderful console.

To be fair, we're only bitching because although they've 'provided' it to us, they still seem to be suffering from the belief that they own it. Right of first sale, guys, right of first sale.

Nemo[ · « **Reply #27 on:** May 16, 2007, 05:46:00 AM »

I'd say the bigger issue is what happens when MS blows the next e-fuse?

If it's around the winter update most of us won't have any warranty left and there's no easy way for J6P users to claim manufacturing error due to bad e-fuses.

monkeyflungpoo · « **Reply #28 on:** May 27, 2007, 03:42:00 PM »

QUOTE(Nemo[ @ May 16 2007, 06:46 AM)

I'd say the bigger issue is what happens when MS blows the next e-fuse?

If it's around the winter update most of us won't have any warranty left and there's no easy way for J6P users to claim manufacturing error due to bad e-fuses.

I was reading that, and people like us can tell the courts, that all those 3 Red Lights, were caused by blowing the e-fuse. interesting point?

Author Topic: 2858 to 1888 Kernel 'Downgrade' Confirmed, not working with 4552+ (Read 429 times)