Post by: STICKY_BUD on November 14, 2004, 10:15:00 PM
where to begin, hmmm. lets start with the boxes...
xbox #1
halo se 1.4
purchased from ebgames
first xbl login was march or april 2004
added smartxx via pinheader in may 2004
bios is x2 version 4983.06
loaded 120gb hd - locked w/smartxx 3311
last xbl login was in early october
stock hd st310014ace is locked, uninstalled and untouched
xbox #2
black 1.0
purchased from etoys/kbtoys
first xbl login was back in 2002
added xenium via pinheader in may 2004
removed chip in june to check for clone(chip is still removed, but pinheader & d0 are still installed)
loaded 30gb hd(i have no access to this data) - locked w/ xos 1.1
last xbl login was in late june - tested in order to make sure it worked after removal of clone chip
stock hd st310211a is locked, uninstalled and untouched
xbox #3
stock 1.3
purchased from dell
xbl virgin
it has been turned on once to test
both xbox #1 & #2 were modded after first xbl login and each have their stock eeprom.
due to a very long vacation with my wife and kids, i did not login to xbl between late june and the release of sw battlefront in september.
when i finally did login, i had to grab a dashboard update and i specifically remember when i played again the next day, after using my chip for various purposes in between, that i had to grab the same update. in fact, this may have occurred a 3rd time, but i honestly do not remember for sure.
i guess i played battlefront on xbl up until about a month ago, when a certain 27 day leak occurred. after that, i felt it was best to stay away from xbl for awhile since i figured some drastic steps would be taken by m$ and i was hoping to avoid it.
i have no reason to believe that xbl expects me to have a different hd in xbox #1 since i have successfully played on xbl within the last 5 weeks.
that is where i am now... except after the last few days of reading, i think i could be banned already and in that case, maybe i can at least be useful while i am getting banned messages.
i think it is clear that the best step for xbox #1 is to keep it as i have it right now and see if i can play halo 2 on xbl succesfully. however, should i remove my gt from the system and use a 2 month trial, or is my gt already flagged(since i played on xbl in october)? i have not read enough about this yet and i will do some searching.
i also think that it might be best to test xbox #2 with the stock hd first since an xbl login using xbox #1 might possibly get xbox #1 banned(which would also get my gt flagged).
input from any of you who have been active in regards to this subject is very much appreciated. after we have kicked it around, i will put whatever seems to be the best course of action to the test.
if either xbox #1 or #2 gets banned, then i will leave xbox #3 as is...
This post has been edited by STICKY_BUD: Nov 15 2004, 06:22 AM
Post by: man_of_war2081 on November 15, 2004, 12:20:00 AM
| QUOTE (STICKY_BUD @ Nov 15 2004, 07:11 AM) |
| i have never been banned, i have not tried to login to xbl since october and i currently own 3 xbox systems. basically, i was waiting for halo 2 when all this banning business started and that extended my wait. after reading tum's post(in gumba's very long thread), i realized i am in a very similar situation and i am willing to try xbl again. where to begin, hmmm. lets start with the boxes... xbox #1 halo se 1.4 purchased from ebgames first xbl login was march or april 2004 added smartxx via pinheader in may 2004 bios is x2 version 4983.06 loaded 120gb hd - locked w/smartxx 3311 last xbl login was in early october stock hd st310014ace is locked, uninstalled and untouched xbox #2 black 1.0 purchased from etoys/kbtoys first xbl login was back in 2002 added xenium via pinheader in may 2004 removed chip in june to check for clone(chip is still removed, but pinheader & d0 are still installed) loaded 30gb hd(i have no access to this data) - locked w/ xos 1.1 last xbl login was in late june - tested in order to make sure it worked after removal of clone chip stock hd st310211a is locked, uninstalled and untouched xbox #3 stock 1.3 purchased from dell xbl virgin it has been turned on once to test both xbox #1 & #2 were modded after first xbl login and each have their stock eeprom. due to a very long vacation with my wife and kids, i did not login to xbl between late june and the release of sw battlefront in september. when i finally did login, i had to grab a dashboard update and i specifically remember when i played again the next day, after using my chip for various purposes in between, that i had to grab the same update. in fact, this may have occurred a 3rd time, but i honestly do not remember for sure. i guess i played battlefront on xbl up until about a month ago, when a certain 27 day leak occurred. after that, i felt it was best to stay away from xbl for awhile since i figured some drastic steps would be taken by m$ and i was hoping to avoid it. i have no reason to believe that xbl expects me to have a different hd in xbox #1 since i have successfully played on xbl within the last 5 weeks. that is where i am now... except after the last few days of reading, i think i could be banned already and in that case, maybe i can at least be useful while i am getting banned messages. i think it is clear that the best step for xbox #1 is to keep it as i have it right now and see if i can play halo 2 on xbl succesfully. however, should i remove my gt from the system and use a 2 month trial, or is my gt already flagged(since i played on xbl in october)? i have not read enough about this yet and i will do some searching. i also think that it might be best to test xbox #2 with the stock hd first since an xbl login using xbox #1 might possibly get xbox #1 banned(which would also get my gt flagged). input from any of you who have been active in regards to this subject is very much appreciated. after we have kicked it around, i will put whatever seems to be the best course of action to the test. if either xbox #1 or #2 gets banned, then i will leave xbox #3 as is... |
Keep us posted
Post by: Gumba on November 15, 2004, 12:47:00 AM
that way if you *do* get your gamertag flagged, your real one will still be safe
I guess you're first xbox should be tested as is
not sure what the best course of action for your second box is
This post has been edited by Gumba: Nov 15 2004, 08:49 AM
Post by: DeMoN_DARREN on November 15, 2004, 03:48:00 AM
So instead heres some good luck man!!!
Keep it up!!!
Post by: nfs911 on November 15, 2004, 04:28:00 AM
This post has been edited by nfs911: Nov 15 2004, 12:41 PM
Post by: Gumba on November 15, 2004, 05:07:00 AM
| QUOTE (nfs911 @ Nov 15 2004, 01:24 PM) |
| I got a new hd, a new eeprom, and a new gamertag, I put in halo 2, got the update, then I left xbox live at the main xbox live screen for around 3 hours. I havent been banned yet this morning. Imma leave it on for 30 minutes cause I got school, when I get home, Ill tell you if im banned. I have apps on E, and dashboard on C. Xenium. my 120gb hd is a seagate (A seagate came with my xbox). I went to memory on xbox, and I deleted all modded files. |
I think you'll be safe
Post by: STICKY_BUD on November 15, 2004, 01:19:00 PM
condtions for test 1
- attempt xbl login with xbox #1 with the large hd and a new gt tonight.
- login again tomorrow(tuesday) night and a third time on wednesday night.
- no ban would mean that xbox #1 is married to the larger hd which was installed in june.
- it would also suggest that the eeprom/hd serial marriages started upon the dash update which was released after june 30, 2004(august?), since i was off xbl for the 10-12 weeks from that june date until late september when i signed in and updated my dash.
- if xbox #1 gets banned, then that either means that i was pre-banned by the m$ dash because i might have accessed it with modchip on(not sure about that), or less likely, that i was flagged sometime between the dash update and my last xbl login(auto-login disabled and x2 4983 bios).
- a ban could also suggest that the marriage took place before my hd upgrade in june, but according to several posts i have read, and trust, i do not think this is the case.
edited test 2 - see below for new conditions
This post has been edited by STICKY_BUD: Nov 16 2004, 12:10 AM
Post by: airviper127 on November 15, 2004, 01:58:00 PM
keep us posted. 
Post by: STICKY_BUD on November 15, 2004, 04:08:00 PM
case 1 for test 1 - should test 1 result in a ban by wednesday night, the conditions for test 2 will be...
- call 18004myxbox and cancel new flagged gt
- reinstall the stock hd into xbox #2 and register new gt to attempt xbl login(this test will commence immediately after ban from previous test).
- login again for 2 more nights.
- in this case, we can assume that the stock hd in xbox #2 will pass any hd scan that might be run
- if xbox #2 does not get banned by the weekend, that would further prove that the marriage took place after june 30, 2004 since my last login with this box was prior to this date with a larger hd installed.
- no ban may or may not add proof that xbl is not bothering to check the lpc/d0 since xbox #2 still has the pinheader and d0 wire soldered in.
- no ban would also likely suggest that the marriage for xbox #2 will in fact take place on wednesday night at my first dash update since june.
- if xbox #2 gets banned, then that suggests that xbl could be scanning the lpc/d0, but i suspect this will not occur(ban).
- a ban could also suggest that the marriage took place in june when i was connected to xbl with my larger hd, but according to several posts i have read, and trust, i do not think this is the case.
case 2 for test 1 - should test 1 not result in a ban by the time i run my tests on wednesday night, the conditions for test 2 will be...
- install larger hd into xbox #2 before i test it and attempt xbl login on wednesday night with the same gt used in test 1.
- login again on thursday night and friday night.
- in this case, we can assume that the hd in xbox #2 will not scanned for sw
- if xbox #2 does not get banned within 3 nights of xbl gameplay, that would suggest that the marriage for xbox #2 will take place when it receives the first dash update since june(upon registering new gt or first login).
- no ban may or may not add proof that xbl is not bothering to check the lpc/d0 since xbox #2 still has the pinheader and d0 wire soldered in.
- if xbox #2 gets banned, then that suggests that xbl could be scanning the lpc/d0, but i suspect this will not occur(ban).
i am going to start these tests in 3 hours. however, before i run the tests tonight, i have a question. how do i remove my old gt from xbox #1? is there anything to do besides removing the save file in the menu?
first update will be posted later... hopefully, a little while after my first round halo 2 mp butt-whooping. now, who will be doing the whooping is the only question. pm me to let me know if you will be playing too and i will look for you. :-j
This post has been edited by STICKY_BUD: Nov 16 2004, 12:34 AM
Post by: STICKY_BUD on November 15, 2004, 09:11:00 PM
i successfully logged in tonight using xbox #1 with the old gt - i got excited to play halo 2 on xbl and too lazy to make a new one. i was required to download another update tonight as soon as i tried to sign in, but maybe that is just routine these days; i have not tried xbl for over 5 weeks now and this one did not take very long - 5 seconds. i even had a voice message waiting for me from an old g.r. buddy who was playing halo 2 already tonight and that was very cool. i like the gameplay, but only stayed online for about 20 minutes. i will definitely be online again later tonight and play for a couple of hours.
as long as i am not banned, i will resume my testing tomorrow evening and report back here after the first 24 hour cycle of test 1.
if i do get banned, then test 2 will begin.
Post by: STICKY_BUD on November 16, 2004, 09:36:00 AM
a ban would flag my gt and that would allow me to test other thoeries regarding the extra scans that users have said they suspect xbl might be running anytime a gt which was being used during a ban tries to login. however, i suspect somebody must be trying those theories out too so i will keep looking for that too.
here is syntax;error's thread:
http://forums.xbox-scene.com/index.php?showtopic=307503
Post by: STICKY_BUD on November 17, 2004, 12:43:00 PM
* it appears from my test, as well as several other reports, that the live 2.0 dash update released in late summer, or one of the updates that followed, is the start date for the xbl marriage of your eeprom and hd.
* it appears from my test, as well as several other reports, that if your box is stock or modded version 1.4(or lower) and has never been connected to xbl, you are not married to your hd and can reconfigure your box as you please BEFORE connecting to xbl without worry.
* it appears from my test, as well as several other reports, that if your box is stock or modded version 1.4(or lower) and has connected to xbl, but has also never received the live 2.0 dash update(in other words, you have not connected to xbl since june/july 2004), you are not married to your hd and can reconfigure your box as you please BEFORE connecting to xbl without worry.
i cannot think of any tests to attempt with xbox #2 and/or xbox #3, so i will not be taking the risk of connecting these UNLESS for some reason, i receive a ban before the end of the week. if i do receive a ban, i will have to assume that a new update(after today) made me vulnerable.
peace!
This post has been edited by STICKY_BUD: Nov 17 2004, 09:02 PM
Post by: vintster on November 17, 2004, 01:15:00 PM
Post by: revengeismyfury on November 17, 2004, 01:39:00 PM
This post has been edited by revengeismyfury: Nov 17 2004, 09:40 PM
Post by: SYNTAX;ERROR on November 17, 2004, 03:13:00 PM
Post by: STICKY_BUD on November 20, 2004, 02:00:00 PM
additional info... i upgraded xbox #2(last used in june) today from the 30gb hd that was there to a new much larger hd using a new smartxx 2.0 to clone, unlock and lock the drives. this time i used os 3325. xbl login did send me to the network troubleshooter, but all i needed was to fix my network issues and then, no problems.
bottom line is that i have used the modchip sufficiently to say that i feel very safe using my xbox as i normally would, including for playing online without receiving a ban.
good luck xbox-scene users. let me know if you think i can help answer a question or can clarify anything in this thread for you.
*edit for clarity
Post by: STICKY_BUD on November 20, 2004, 06:59:00 PM
| QUOTE (Fofer @ Nov 20 2004, 04:22 PM) |
| Thanks for the clarification, Sticky_bud. My own modded Xbox (now still on Live) seems to happily confirm your summary. Does this only come into play once Halo 2 is run (and the dashboard update it applied?) I ask because I haven't bought Halo 2 yet. Been playing Crimson Skies all week though without issue. I was thinking about picking up Halo 2 but didn't want to do so if I'd get banned simply from launching it. |
if you have been online with your modded box anytime since the live 2.0 dash update, as far as xbl is concerned your hd is married to your box - halo 2 is a non-factor.