Update is out and everything still works apparently

[vwvSTATICvwv]

I've seen a few people confirm that the backups still work & also on live. Who knows if MS is just sitting on this though? 
Either way, just giving everyone a heads up! 

[vwvSTATICvwv]

I can now confirm it as well 

[Arakon]

live bans take 24 hours to trigger, so don't get too happy just yet.

[vwvSTATICvwv]

Oh noes...don't tell me that man, that would suck! 

[uberfry]

go back to original fw when playing on live

[elitedev]

on the microsoft website it lists all 125 new features for the update... near the end i see this 'Better support for Xbox 360 game disc recognition' ... that doesnt sound to assuring.

[Havok]

I having "upgraded" my Samsung DVD yet. (had to order a SATA card).  I was going to perform the update and then thought they could have easily fixed the whole where you can not backup / write the firmware with the current tools.  I decided not to take the update for now..

[stonersmurf]

on the microsoft website it lists all 125 new features for the update... near the end i see this 'Better support for Xbox 360 game disc recognition' ... that doesnt sound to assuring.

I think what they mean is, instead of the button on the dash just saying play game is will say play GRAW or play Madden. But I could see ms using the time bomb effect. Spend atleast 24 hours waiting and letting every buddy log onto live then in one strike ban them all. Makes sense. I wouldn't update till you come by a game that you have to update to play.

[Dzgx216]

go back to original fw when playing on live

  I'm not sure that they can detect it unless you're actually using a backup disc in the drive.  The most plausible method would be to check physical data located on the disc through the process of a the console sending an unexpected command to the drive.  Thus, they would get a read on something we haven't set up the disc to spoof.  Not sure about the idea of dumping the contents of flash and checking the checksum.  Just doesn't seem plausible to me.  I would think they would stray from doing anything involving the flash.

[MacDennis]

  I'm not sure that they can detect it unless you're actually using a backup disc in the drive.  The most plausible method would be to check physical data located on the disc through the process of a the console sending an unexpected command to the drive.  Thus, they would get a read on something we haven't set up the disc to spoof. 

Long before the new dashboard arrived, a completely normal command was already transmitted to get the physical format information from the disc. The data which is returned to the console screams: 'I AM A BACKUP'.

A dashboard and/or game update can check the contents of this data very easily. Why they aren't checking it is anyone's guess ..

[pablot]

if I was microsoft I would simply collect data and let people run with the firmware for a while and then slam everyone that has been using it at the same time and ban them from live. That way they'll make people too paranoid to go on live with a new modified firmware that is protected against the first check etc.

[Havok]

  I'm not sure that they can detect it unless you're actually using a backup disc in the drive.  The most plausible method would be to check physical data located on the disc through the process of a the console sending an unexpected command to the drive.  Thus, they would get a read on something we haven't set up the disc to spoof. 

Long before the new dashboard arrived, a completely normal command was already transmitted to get the physical format information from the disc. The data which is returned to the console screams: 'I AM A BACKUP'.

A dashboard and/or game update can check the contents of this data very easily. Why they aren't checking it is anyone's guess ..

Maybe they are checking and just collecting data..  Or they are just working on more fixes.  I still think the user base with the hack is very small.

[sparkstr]

live bans take 24 hours to trigger, so don't get too happy just yet.

My wife logged on with my original xbox running evox about a year ago and the ban was instant.  If you are assuming that microsoft is going to sit for 24 hours and let database of hackers accumulate then you should say that this is speculation.

[Arakon]

I know it for a fact. a friend of mine went online in GR2 with the chip turned on on my xbox, played for several hours, I tried again in the evening and it still worked, and the next day it was banned.

[elitedev]

i think if they fixed the firmware hack it would be listed as feature of the update.

[Arakon]

I doubt it. that'd basically be like admitting that it's a big issue. they're trying to play it down.

[elitedev]

it is a big issue to the shareholders and developers. it would be listed. microsoft takes pride is crushing pirates.

[Arakon]

did they announce the blocking of the kiosk disk? nope.

[Interloper]

if I was microsoft I would simply collect data and let people run with the firmware for a while and then slam everyone that has been using it at the same time and ban them from live. That way they'll make people too paranoid to go on live with a new modified firmware that is protected against the first check etc.

  Like I said before, they're still making money on the live customers, REgardless. If you are the xbLive executive.. the 'dead give-away' time
to ban the hackers would be when the little XboxLive Bandwidth Flowchart shows the need for more servers to accomadate clients. Until then, its up to them to take some funds, or not. Some* cheese is there for them to take

..and the mouse runs to the cheese, then the cat to the mouse.. poor M$.. decisions decisions..

  They know you're still going to play offline REgardless. A feasible approach to the lengthy delay of hack-fixing updates would be to counter it in its entirety THEN ban(maybe making a bit more than a cat-and-mouse game). The counter would take more time than we've given them so far.

[Dzgx216]

  I'm not sure that they can detect it unless you're actually using a backup disc in the drive.  The most plausible method would be to check physical data located on the disc through the process of a the console sending an unexpected command to the drive.  Thus, they would get a read on something we haven't set up the disc to spoof. 

Long before the new dashboard arrived, a completely normal command was already transmitted to get the physical format information from the disc. The data which is returned to the console screams: 'I AM A BACKUP'.

A dashboard and/or game update can check the contents of this data very easily. Why they aren't checking it is anyone's guess ..

  Yeah, I should have worded that better. I'm sure you already know (maybe not everyone else) that in the hitachi It's stored in RAM at 3bab0.  All of my dumps say RITEK in the ascii side.  It's definately interesting that it's not being check as of yet.  It would be rather easy to modify the FW to read the PFI from its on-disk location and do something similar to the SS relocation.  I looked at 3 dumps and came up with the same PFI for all:

24 02 F2 80 dc 88 00 00 00 00 00 00 01 02 31 10
00 03 00 00 00 FC F8 9E 00 03 0A 8F 00 00 00 00

So locating that in a different sector should be too much more difficult than the original SS relocation.  It's read in a different fashion, but that's because I think it is read regardless of some of the other mini-checks here and there that determine xb1/360/DVD/CD.