Print

[Gumba]

QUOTE (xbox_Steve @ Dec 18 2004, 12:11 AM)

what do u mean by that? once a hard drive is locked isn't the xboxdash.xbe regular and normal like before?

uh.... no

The xboxdash.xbe is only regular and normal if you haven't modified it (or replaced it) or if you have and then restored it back to being a regular and normal one.

[xbox_Steve]

QUOTE (Gumba @ Dec 18 2004, 03:21 AM)

uh.... no

uh... ok

[[GS]EqUaTe]

Well, make sure that you use an empty or non-existant disk.bin when you recreate the partitions.
Before you set up the new GT, use the mod mode to take a backup of your eeprom and such, then have a look in disk.bin with a hex editor, and make sure xbox.com does NOT appear in it anywhere.

Assuming all of that goes fine, you should be able to use it w/o getting banned, with a large hd.

[Aaries]

Ok, dumb question time.  Where is the disk.bin file located so I can view it?

[xbox_Steve]

QUOTE ([GS)

EqUaTe,Dec 18 2004, 03:26 PM]Well, make sure that you use an empty or non-existant disk.bin when you recreate the partitions. Before you set up the new GT, use the mod mode to take a backup of your eeprom and such, then have a look in disk.bin with a hex editor, and make sure xbox.com does NOT appear in it anywhere. Assuming all of that goes fine, you should be able to use it w/o getting banned, with a large hd.

could u explain that a little more? i'm not sure i understand how to do that
thanks

[Angerwound]

QUOTE ([GS]EqUaTe @ Dec 18 2004, 09:26 AM)

Well, make sure that you use an empty or non-existant disk.bin when you recreate the partitions. Before you set up the new GT, use the mod mode to take a backup of your eeprom and such, then have a look in disk.bin with a hex editor, and make sure xbox.com does NOT appear in it anywhere. Assuming all of that goes fine, you should be able to use it w/o getting banned, with a large hd.

This is a bunch of bullshit. I have looked into this and makes no sense at all. How are you going to tell me that this 'file' is storing info about your live accounts. I have used the same xbox for live since day 1. This box has been banned more times than you can imagine, around 50 times to date. Each and everytime was for something dumb on my part, nothing 'mysterious'. It has had it's live accounts terminated twice. Now, everytime I needed to get back onto live. All I did was change the eeprom and create a new gamertag. There were occasions that I did clean the hard drive of 'other files'. But this was back when I believed them to be scanning the contents of the drive. I have slowly been keeping shit on my hard drive and still have not been encountered with a ban yet. Therefore, if this theory was correct this disk.bin would have kept me from staying unbanned. The only 'theories' I see as possible remaining true is the check of 'xboxdash.xbe' and the marriage of an eeprom and harddrive when you create an xbox live account ( could explain why I need to create a new gamertag to stay unbanned since the 'security updates' ).

Anyways, just my two cents.  

[xbox_Steve]

well what i did was just get a eeprom, changed it with config magic and got a new code and GT
and am hoping no ban....

[xbox_Steve]

i got banned again, so it must check something in my harddrive, so i'm goann try again with my old harddrve and clean it out and everything. I hope that works

[xbox_Steve]

QUOTE(    @ Dec 20 2004, 01:24 AM)

Ok, heres my question. If I bought a new hardrive and a virgin eeprom(never touched live) and use my old gamertag will I be good to go? Now see the thing is my current xbox drive/gamertag havnt been banned Im pretty sure I just keep on getting a live not found error. So would that work or would I need a new gamertag too?

[Angerwound]

QUOTE(zoomer777 @ Nov 20 2004, 12:56 AM)

Since everyone out there is spitting out theories on the reasons why, and very few seem to know what they are doing...it's crazy to assume anyone is "right"

[[GS]EqUaTe]

That will be fine. I'm using that setup myself now, because I didn't want to lose my GT.

Angerwound: disk.bin is not a file, and my feeling as to why you didn't get rebanned quickly in those cases is due to ONLY changing the hdd key and creating a new gamertag. This could, of course, be wrong.
Disk.bin is formed of data stored on the hdd, effectively the partition table, or part of it. Possibly the boot sector (though I doubt that myself). It is created when you use the backup function in EvoX. If you open it with a hex editor, you will find two mentions of xbox.com with regards to passports. One account is your xbox, the other is your GT. It's covered in better detail in other threads.. Such as the What we know (fact) thread.. (Or whatever it's called).

Anyways.

[bgrill27]

QUOTE

My box is an Xbox Ver 1.0 (ancient) with an X2-Lite 2.1 Mod chip in it! I have a 100GB upgraded hard drive that has been faithfully in place for practically 2 years!

I too have an old v1.0 box and had the "cannot connect" message appear shortly after I put in a big HD and modded it. I did not get the "console has been modified" message and called tech support. After reading them the error codes they said it was an error on their part and that they would fix it for free (out of warranty.) Because I had a modded box I didn't send it in and instead bought a new EEPROM. I was fine until today when I got the "your console has been modified" message. I do not think you were originally banned because of  MS's detection. It was probably a problem with the v1.0 boxes. Does anyone remember all that talk of the old boxes not being able to connect?

[kingnbajam]

 

[bgrill27]

kingnbajam, I assume you flashed with a new EEPROM? Did you make sure you configured all the settings in XBL setup correctly? If you try to connect again does the your console has been modified message appear?

[kingnbajam]

QUOTE(bgrill27 @ Jan 2 2005, 08:10 PM)

kingnbajam, I assume you flashed with a new EEPROM? Did you make sure you configured all the settings in XBL setup correctly? If you try to connect again does the your console has been modified message appear?