Print

[mc_365]

First hand,

Played Live for years on V1.0 box with x2.2 pro disabled.
Aug Put in a 200Gig HD.
Continued to play live with chip disabled.
Stop Playing live in late sept.
Heard about banings in Oct. so I stayed away from live.
Purchased Halo2 did not play live.
Heard about bannings ~Nov 9.
Stayed off Live.
Nov 20 said fuck it.
Formated C: E: then returned to stock using slayers 2.5 on big HD.
Booted retail.
Put Mem card with live account in.
Signed in with password.
Put Halo2 in.
Took Long updated.
Played Halo2.
Next Day Banned.

[Seraph_Six]

QUOTE

I had been troubleshooting a modded xbox with my gamertag, because it wouldn't connect to XBL. Turns out the box ended up being banned for being modified. Now, I just tried to log into XBL from my modded box, which had mo major changes since I had started using Live on it, and never violated any of the "rules" beforehand... Box is banned I think that the tags are DEFINTELY being marked for being used on a modded box, and thus doing more extensive scans. There's no explaining my banning otherwise

[Gumba]

QUOTE (xprezz @ Dec 6 2004, 05:57 PM)

Any news in this matter? The cookie stuff is really interesting, I would love to see some more test results (low level formats, previously banned GT etc). I may have missed it, but I have yet to see confirmation that the following works: Situation Banned xbox Large harddrive (the one that was in the box on banning) GT (the one used for signing in when ban occured) solutions Fresh EEPROM Low Level Format to clear cookies (sames HD as when ban occured) Sign in using the same GT that was used when Ban occured. I have access to an Xbox with a large HD, banned EEPROM, "banned" GT. So I can test the above scenario and give results. What the quicktest/cheapest way to get hold of a new virgin eeprom? Also a small prayer: Could people with "I just bought an Xbox how can I avoid getting banned" etc post keep it out of here. This is a fact finding post, trying to get to the bottom of things. Also: Halo 2 on modded xbox, Large harddrive, non stock files on E:, F: drives etc DONT get you banned. Being careless with a modchip, not disabling auto signin in the xbdash etc gets you banned. And I dont care what your "friends" have experienced, I want first hand, fact based posts. Anything else is useless. lets get back on track people.

The reason you haven't seen any confirmations is because there have been plenty of confirmations that the Flagged GT thing is true and thus even if you revirginize the HD and use a new EEPROM you still have to use a new GT if your old one is flagged. (and your drive is not a stock drive)

[dalime]

Before anyone asks; my chip was never on and the x3 has live blocking anyway.  I never ran Halo2 or updated during these test.  I stricktly signed into the friends list from the dash.  This is all on a V1.3 w/ a Xecuter 3 chip and a 120gb WD.

It seems to me that although the disk.bin and marriage theory seems to be the best and most probable so far, fixes that have worked for some are not working for others.  Which leads me to believe that there is some level of randomization with whatever kinds of checks/scans that M$ is doing.  I felt certain after doing test #2 that I would be back on, at least for more than 12 hours!

Thanks to all the guys that go home (or stay home   ) everyday and mess with their xbox's trying to figure this out.  Even though everyone is not back up yet, it feels like we are definitely making progress.

[elemenopee]

I have a question (and maybe this has been answered already)... I just replaced my stock HD with a 200gig WD.  Prior to this I had created my XBL account on my stock drive.  When I fired up my new drive after setting it up (mod chip off ofcourse), my live account was not on my new drive so I did used the 'account recovery' feature.  Now, this can be used so you can log in from a different xbox to play with your account.  Would the revoery feature clear out the marriage info between the hd and eeprom?  I was able to connect to live on my new drive, recovery my account, and edit my friends list with no problem (no modded xbox error).  

I'm a little hesitant to play a game on it, I may end up just setting my box up so that I can easily swap between my stock drive nad my new drive.

[Gumba]

QUOTE (sparkfarmer @ Dec 7 2004, 09:33 AM)

Gumba, what is the status of your xbox now? Are you still on live with the config that you have in your sig? I am about to join up for live. I have the same setup as you and would like to know if your box (with the config of your sig) still good. Also do you have any files on C: or E: that are not standard? Thanks.

Sure, 100%, and everyone I've ever done a mod for is also on Live still.

I have a c:\bios folder which contains an XOS folder and a few bios folders (like my tweaked 4981 etc)

I also have my avalaunch files on c:

I have all my apps on e:\apps

and I have lots and lots and lots of saves from various emus and apps.

I have never pirated H2 or loaded a hacked game save or a font exploit, or cheated online.

[Gumba]

QUOTE (dalime @ Dec 7 2004, 04:52 AM)

Bump....and I'll add some experience from the recent tests I've done. 1. Low level formatted drive (before we knew we didn't have to do this), re-installed drive via Slayer's 2.6.  Everything non-M$ on F:.  Used a two month trial and recovered my banned account.  I was banned by the next morning. 2. Manually installed and reconfigured drive with Evox "ConfigSector" command and a clean disk.bin file.  Only non-M$ files were Evox on F:.  Used original backup of my stock drive for C:.  Used a two month trial and created a NEW account with a different CC (for the hell of it).  Banned by next morning. Next I will try the same as #2 but with an older dash version.  I don't know if this will make any difference at all.  If that doesn't work I will try test #2 but with my stock drive.  If that doesn't work I will try with my stocker but pull my chip and see what happens.  After that.... I don't know.   Before anyone asks; my chip was never on and the x3 has live blocking anyway.  I never ran Halo2 or updated during these test.  I stricktly signed into the friends list from the dash.  This is all on a V1.3 w/ a Xecuter 3 chip and a 120gb WD. It seems to me that although the disk.bin and marriage theory seems to be the best and most probable so far, fixes that have worked for some are not working for others.  Which leads me to believe that there is some level of randomization with whatever kinds of checks/scans that M$ is doing.  I felt certain after doing test #2 that I would be back on, at least for more than 12 hours! Thanks to all the guys that go home (or stay home   ) everyday and mess with their xbox's trying to figure this out.  Even though everyone is not back up yet, it feels like we are definitely making progress.

Did you change your eeprom too?

You have to change your eeprom

[Gumba]

QUOTE (elemenopee @ Dec 7 2004, 04:22 PM)

I have a question (and maybe this has been answered already)... I just replaced my stock HD with a 200gig WD.  Prior to this I had created my XBL account on my stock drive.  When I fired up my new drive after setting it up (mod chip off ofcourse), my live account was not on my new drive so I did used the 'account recovery' feature.  Now, this can be used so you can log in from a different xbox to play with your account.  Would the revoery feature clear out the marriage info between the hd and eeprom?  I was able to connect to live on my new drive, recovery my account, and edit my friends list with no problem (no modded xbox error).   I'm a little hesitant to play a game on it, I may end up just setting my box up so that I can easily swap between my stock drive nad my new drive.

It sounds to me like you're now in the pre-ban limbo.

We're not actually sure what to do in that situation.

I would suggest getting a new eeprom before you go back online

[dalime]

QUOTE

Did you change your eeprom too? You have to change your eeprom

Kind of an important step to leave out.     Guess I just figured that would be a given.  Yes,  I changed eeprom everytime.

[dalime]

QUOTE

in your case .. the reason you were banned twice is because of a flagged GT on a bigger drive

I established a NEW account when I performed test 2.

[dalime]

When I was configuring my drive for test 2, I used the "configsector" command from my Evox dash on F:\.  After doing this I used the backup command to double check that it was clean, but the old disk.bin from test one was still there with my banned GT and SN.  Sooooo, I ran "configsector" again but placed the disk.bin from a Slayer's disk into the F:\ directory with my dash.  Ran backup again and there was the Slayer's disk.bin.  Installed the new eeprom (can't forget this) and set up a new account.  Banned!
Should I not have used the file from the Slayer's disk?  The original disk.bin from my stock drive already has my old banned GT and SN on it and I wouldn't even know where to begin to remove the "cookies" with a Hex editor.

[dalime]

[Gumba]

There are other methods used to ban people. You should read the entireity of the first post as it contains fairly definitive coverage.

For example, if you have replaced c:\xboxdash.xbe with a non MS dash, then you can get banned, if you have a flagged GT or if you have a font exploit installed.

[Gumba]

See the "Local Marriage Theory" section in the first post.

QUOTE (slyt PM)

Touch wood, yes and that means Ive gone through the big 72 hour mark !! I havent checked it today yet but am going to this evening. I shall try and get a tutorial done over the weekend or this evening if I get time. If you are needing to get yours unbanned, I can help you. In the first instance you will need a new EEPROM, from Zodiak (he has a thread with all the instructions etc. He takes upto 48 hours to give you an EEPROM, so if you need one, best ask now. Dont forget to specify which version Xbox you have, and whether you are a PAL or NTSC user. - my guide is likley to be a little more paranoid than some as it includes formatting the hard drive, replacing the EEPROM etc. I feel this is the "safest" option and so far seems to work ! slyt

[Skywalker]

so you tell that hd must be changed before register a game tag that means connect to xbox live and you also tell that i need to preserve my hdd key and my hdd serial number in the bigger hd...

how can i do that?

how can i make my bigger hd the same (for hdd key and hdd serial number) that the original one?