Print

[deltop]

QUOTE(addisj @ Nov 2 2006, 01:14 PM)

Thanks for clearing that up - Well I definately cant update my box then having a Sammy instead of the original Hitachi!

I swapped drives from a Hitachi to a Samsung a couple of weeks ago, and got no error after updating. Currently using the 4.1a firmware if that helps. As others are reporting you just re-flash anyway to get rid of the error.

[Kramer987]

can't there be a way to remove the update files from game discs? i feel like after backing up the structure of the disc can be examined and the brilliant minds who bring us all the good stuff already might be able to figure something out. i think that seems plausible. with xbox1 we were able to remove updates completely in order to turn dvd9 into dvd5. i feel like something similar can happen in this case.

[deltop]

QUOTE(Kramer987 @ Nov 2 2006, 01:46 PM)

can't there be a way to remove the update files from game discs? i feel like after backing up the structure of the disc can be examined and the brilliant minds who bring us all the good stuff already might be able to figure something out. i think that seems plausible. with xbox1 we were able to remove updates completely in order to turn dvd9 into dvd5. i feel like something similar can happen in this case.

It's not possible to tamper with the file structure AT ALL. Read up more on the firmware hacks to see why.

[d-range]

QUOTE(Trex666 @ Nov 2 2006, 10:20 AM)

If microsoft do have the capability to update the firmware on a flash, this could be the first step of a plan.
Microsoft could update the firmware on the DVD drive, and lock the version of the firmware in the kernel so you cant downgrade.
Sounds like a strat

This is very, very unlikely for the following reasons:

1) Flashing remotely could brick a lot of unmodded boxes, seeing that they get the E66 as well at the moment.
2) MS released a flash-blocked drive themselves (ms28), so it seems unlikely they even WANT to do remote flashing
3) All xboxes that have a broken & swapped dvd drive either need to be flashed or will stop working
4) People that mod their drives can easily flash back and put a blocked firmware on, like the firmguard Xtreme versions. Or just the hacked fw based on the exact revision that was originally on the drive.
5) It doesn't make sense. The percentage of hacked boxes is already pretty small, new 360's are just too hard to flash for most people (thanks to the black glue), and those smart enough to fix their flashed fw after a flash by MS will just keep their box off the net.

Id sooner expect they only try to gather information on the drive/firmware/box combination, and use this later for XBL bans. And messed up pretty badly by performing calls that do not work across all fw versions.

At first I didn't think E66 had to do anything with hacked fw at all, but I'm getting pretty convinced now that MS is at least TRYING to do something to detect modded fw. I wouldn't be surprised if they already have a nice list of modded boxes that succesfully updated, without the owners knowing they're already flagged.

[PhatheadWRX]

This makes me think the good ol' MS is data mining again like they did with hard drives before the banhammer right before Halo 2.

This worries me especially as I have a ms28 fw (4.2) on a ms25 drive, hence I would have updated.  I'm fine on live now however.  Also if they are possibly data mining I want to keep my ms28 fw on the drive and not downgrade to ms25 because that would likely send a red flag.

It seems like 3.3 is the safest bet for ms25 users as long as you can get it on before the update.  Lets all cross our fingers and keep trying to hide from this cat.

[OriginalCompGeek]

Well, MS25/4.1a FW user here.

[PhatheadWRX]

See the thing that sucks is if MS is data mining and does start banning, likely the only people they can get are those with ms25 and 4.0+ fws.

Because they know there was an upgrade to ms28.

If they do start banning, I hope it comes sooner (GOW next week) rather than later (Halo 3 who knows when).  I'd rather not have a false sense of security

[supaspic]

Ok please have patience as to I am unfamiliar to the jargon of firmware upgrade and downgrade. But from what I read only Samsungs are being "bricked." A friend of my has a hitachi and his was bricked with E66 after the update. Just for reference he had Xtreme. So I just wanted to put out there that a Hitachi was "bricked" with E66, and please if you can explain why this could have happened if it targeted only Samsung it'd be cool.

[d0ck]

My xbox are swaped..

I got my xbox on release date, and ya'know it failed. GPU artifacts..

Contacted MS, and they replaced it.. Well a month after that one crashed too.

So I sent it in again.. It took them almost two months to give me a console. But the thing is I called and bitched.

They end up accidently sending me TWO 360's. One with Samsung drive and one with Hitachi Drive

The Hitachi drive froze alot, but I liked my hitachi.. My Samsung drive cracked one of my games..

So I swaped them. This was probaly about 6 months ago. I report no problems here. Knock on wood

I use my Samsung to back-up my games. Every since I had to buy GRAW twice. I play nothing but backups. Sucks, could've got a differnt game instead of buying the same game twice..

So I have swaped drives and have no problems what so ever.. I know the the samsung hacked firmware was out cause I was pissed I didn't have a samsung drive at that time.. but when my console game back it had Samsung MS25, and my second console had hitachi 46d. I swaped motherboards due to the the freezing

Both of my were unaffected.. Thing is though I have not tested my other motherboard. Do't think it's ever been updated.

[Heet]

Theyre not data mining me.  Im not connecting.  

[shaunasparks]

I have a launch day xbox 360.  My hitachi 46dj broke so I swaped it with a samsung MS25.  Currently i'm running xtreme 1.0 without any E66.  Maybe the later consoles had bios changes that had the drive version locked in while the newer ones (Launch day etc..) did not have that code put in it.

God I love 1080p!

[Havok]

All I know is... all the people that said MS cant do anything and thought we are invincible!!!

Just shows how wrong you are.  I am SURE MS keeps an error log somewhere in the console.  If you got an error E66, it is probably recorded already... so the flag to set banns is already there.

Maybe they found a way to detect changes in Hitachi too that they have recorded and it just doesnt throw an error flag.

And as far as reports of innocent people being flagged.  Well if you have an original tamper seal, MS can look at the console and probably determine if it was flagged incorrectly.  If so, they will fix it.  If not they tell you to take a hike.

I mean they have to Fix E71 errrors even though a warranty is expired.. as its their fault.

I would also like to note.. look how simple the method they used is... they know how the console is supposed to work, they have the advantage, not us in these situations. They nabbed a bunch of people can make a statement and can work on grabbing others as time goes on.

[SCSI]

I have a launch 360 but it gave the 3 lights of death so I bought a new one with a hitachi drive (don't know which version yet since I haven't opened my new 360 yet) also. I'm keeping the 47DJ on my launch 360 for a backup and I'm I will be able to swap the older hitachi without any problems.

Will I get problems replacing a hitachi with a newer FW with an older hitachi 47DJ?

[Obveron]

Someday (probably after Christmas), Sith Lord Bill Gates, is going to say "You may now initiate Operation 66" and everyone who has ever had E66 will be banned at once.

[noonlight]

I don't mind not having live, but i want to be able to play on the thing, having xbox live silver would be good too as i like arcade games. Maybe if having a hitachi in a samsung console is a problem i can switch the console on with th samsung in and swap over to the hitachi once the check has been performed?

oh and i don't think bill gates gives much of a crap about that kind of stuff nowadays