Well i just got banned!!!!!
- Thread starter Zaine
- Start date
ok remember if you do get banned i tinhk you can play online using the "xlink kai evlution". you could sign up for a free account and play with people all over the world.
ok for people that modd their 360's for warranty purposes:
no need to mod them anymore as xbox is coming out with the broken game replacement program.
http://www.xbox.com/en-US/support/systemuse/xbox360/gameplay/discreplacement-program.htm
Feel so bad for pirates now.
no need to mod them anymore as xbox is coming out with the broken game replacement program.
http://www.xbox.com/en-US/support/systemuse/xbox360/gameplay/discreplacement-program.htm
Feel so bad for pirates now.
i feel bad for your education cause you still can't read!Albibx said:
"This program only applies to games where Microsoft is the publisher, and is subject to availability."
The following game titles are currently available for this program:
* Crackdownâ„¢
* Fuzion Frenzy 2
* Gears Of War®
* Halo® 2
* Kameoâ„¢: Elements of Powerâ„¢
* Ninety Nine Nightsâ„¢
* Perfect Dark Zeroâ„¢
* Project Gotham Racing® 3
* Viva Piñata™
* Xbox Live® Arcade Unplugged Vol. 1
yeah that solves everything how about GRAW? Rainbow6? Madden? Ncaa? MLB? Fight night? etc must i continue.
MOD EDIT - I suggest you stop with the pointless name calling
im still on live 2 hours in no ban, what the hell is happening????????????????????????????????????? hitachi 47 latest c4eva firmware and playing back ups
oh sorry i ddin't pay attention to that. yess now that means that we still have an excuse for modding.
after talking to some friends im beginning to think their is some means to this madness. MS might have a system log which keeps track of your system and its FW. Its called a mode test.
1. I went on XBL with my original 360 and original FW first (Ms logged my system with that firware code) mode test = 1:1
2. Then i went on XBL again with my FW mod maximus 2.3 (MS logged my same system but this time appeared with a new FW code raising the RED flag) mode test = 1:2
3. Then went on XBL again with my updated FW 2.4 (now this one sytem has been logged in the test with three different FW's) mode test = 1:3
4. All my friends who brought their 360's and modded them straight out of the box before ever going on XBL and never updated or never went back to the original FW are yet to be banned (maybe because for their first time ever going on line their FW reading is the same as it has always been and no changes made so no need to flag it because the FW is stealth anyway) mode test = 1:1
just my theory has anyone that has brought a 360 brand new straight out of the box FW modded it and then went on XBL without ever changing it again and been banned??? my friends have not been banned yet (they are playing Halo3 beta right now with a backup of crackdown)! A mode test is a very easy test to run especially with "stealth FW" but if there are numerous changes than maybe that hinted MS to warrent a ban
1. I went on XBL with my original 360 and original FW first (Ms logged my system with that firware code) mode test = 1:1
2. Then i went on XBL again with my FW mod maximus 2.3 (MS logged my same system but this time appeared with a new FW code raising the RED flag) mode test = 1:2
3. Then went on XBL again with my updated FW 2.4 (now this one sytem has been logged in the test with three different FW's) mode test = 1:3
4. All my friends who brought their 360's and modded them straight out of the box before ever going on XBL and never updated or never went back to the original FW are yet to be banned (maybe because for their first time ever going on line their FW reading is the same as it has always been and no changes made so no need to flag it because the FW is stealth anyway) mode test = 1:1
just my theory has anyone that has brought a 360 brand new straight out of the box FW modded it and then went on XBL without ever changing it again and been banned??? my friends have not been banned yet (they are playing Halo3 beta right now with a backup of crackdown)! A mode test is a very easy test to run especially with "stealth FW" but if there are numerous changes than maybe that hinted MS to warrent a ban
Hmm...that actually made sense. There may be some substance there. Excellent post anyhow.rlash33 said:
Hmmm, I like your theory... Its very likely you may be right. We will all find out eventually. But I have tipped my hat to microsofts 360. Getting a PS3 in a week, Good luck to all those who wish to stay with the 360.
-ShaX
-ShaX
I think that theory might be correct.
I bought my Premium 360 back in early Feb. and immediately modded it. I never even turned it on before then. I made sure I modded it correctly or else it was gonna get returned.
After I modded it (thanks 'txt'_, and had my fill of testing backups, I finally got on the 1-month free trial of LIVE that was given for free. So that means I've always had the same fw since being on LIVE, the 5.3a fw on the MS28.
Other notes:
Used backup copy of Crackdown to DL the beta and play the beta. Have bought and used both: 1-Year prepaid LIVE sub., and 1000 MS points.
1) I'd like to know of anyone that has NOT been banned, and also has rotated their fw more than once (updating fw, or reverting to original) , between the time period where the console first experience LIVE until present.
2) If there anyone that IS banned, if they have stuck to just one fw all the while on LIVE (same time period). I'm assuming there might be other factors here; since there are reports of legit players (no modded system) being banned (hopefully they are telling the truth), there might be other indicators or signals that MS is looking for, besides only a fw change since being on LIVE.
I bought my Premium 360 back in early Feb. and immediately modded it. I never even turned it on before then. I made sure I modded it correctly or else it was gonna get returned.
After I modded it (thanks 'txt'_, and had my fill of testing backups, I finally got on the 1-month free trial of LIVE that was given for free. So that means I've always had the same fw since being on LIVE, the 5.3a fw on the MS28.
Other notes:
Used backup copy of Crackdown to DL the beta and play the beta. Have bought and used both: 1-Year prepaid LIVE sub., and 1000 MS points.
1) I'd like to know of anyone that has NOT been banned, and also has rotated their fw more than once (updating fw, or reverting to original) , between the time period where the console first experience LIVE until present.
2) If there anyone that IS banned, if they have stuck to just one fw all the while on LIVE (same time period). I'm assuming there might be other factors here; since there are reports of legit players (no modded system) being banned (hopefully they are telling the truth), there might be other indicators or signals that MS is looking for, besides only a fw change since being on LIVE.
I also like the theory of the mode test but i still think that M$ will not have only one way to detect modified firmware, incorporating many different techniques would yeild a better hit miss ratio. they do not want another ban everyone then whoops and unban everyone again...
time will tell.
I am interested in how many people are on live at the moment??? does anyone know how to do this? Is it possible?
Mantis
time will tell.
I am interested in how many people are on live at the moment??? does anyone know how to do this? Is it possible?
Mantis
i just want to note that im not banned logged on today using a backup, i have a m28 that was flashed with 5.2 and then to 5.3, never played the halo beta or crackdown.
My first post!!! I have been reading these fourms for months now, but it is time I get involved. Here it is:
I have a hitachi 59 was running 2.3 fw did not update when spring update came out. I updated to 2.4 two days ago and was on XBL all day today with disc back-up.
The backup disc I used was Crackdown (my own copy, not scene release) and halo 3.
I would like to comment on something I have observed from scene released backups: I got as a scene relase game (too lazy to back it up myself) that will not work anymore now that I have updated to newest fw and d/l'ed spring MS update. I get the dirty disc error
I think that the issue is a game issue not a fw issue. For instance all games have a unique id and that is why any games that were scene released are showing up on multiple XBL accounts. MS will identify this unique id on multiple systems and ban it.
One last point and then I will shut up. You need to make sure that games have the proper ss, dmi and pfi. This ban could also result from improper use of those sealth files.
Best of luck to all Xbox is still a sick system and I am sad to hear all those wanting to leave for others
I have a hitachi 59 was running 2.3 fw did not update when spring update came out. I updated to 2.4 two days ago and was on XBL all day today with disc back-up.
The backup disc I used was Crackdown (my own copy, not scene release) and halo 3.
I would like to comment on something I have observed from scene released backups: I got as a scene relase game (too lazy to back it up myself) that will not work anymore now that I have updated to newest fw and d/l'ed spring MS update. I get the dirty disc error
I think that the issue is a game issue not a fw issue. For instance all games have a unique id and that is why any games that were scene released are showing up on multiple XBL accounts. MS will identify this unique id on multiple systems and ban it.
One last point and then I will shut up. You need to make sure that games have the proper ss, dmi and pfi. This ban could also result from improper use of those sealth files.
Best of luck to all Xbox is still a sick system and I am sad to hear all those wanting to leave for others
This theory actually makes alot of sense... I am currently still playing my modded system, I play halo 3, but I have a legit copy of crackdown, not even a backup that I use for that, all other backups I only play offline never online, but IF this is how they are detecting it this could be why people with unmodded 360s are getting banned, lets say I buy gears of war from gamestop a used copy, but the guy that owned it before me just made a backup and we both happen to be on at the same time, Microsoft is going to assume I was in on it and ban us both. even though my system was never modded.glu3stick said:My first post!!! I have been reading these fourms for months now, but it is time I get involved. Here it is:
I have a hitachi 59 was running 2.3 fw did not update when spring update came out. I updated to 2.4 two days ago and was on XBL all day today with disc back-up.
The backup disc I used was Crackdown (my own copy, not scene release) and halo 3.
I would like to comment on something I have observed from scene released backups: I got as a scene relase game (too lazy to back it up myself) that will not work anymore now that I have updated to newest fw and d/l'ed spring MS update. I get the dirty disc error
I think that the issue is a game issue not a fw issue. For instance all games have a unique id and that is why any games that were scene released are showing up on multiple XBL accounts. MS will identify this unique id on multiple systems and ban it.
One last point and then I will shut up. You need to make sure that games have the proper ss, dmi and pfi. This ban could also result from improper use of those sealth files.
Best of luck to all Xbox is still a sick system and I am sad to hear all those wanting to leave for others
well as for the first theory about 3 strikes and you're out cant be true for me, iv had my 360 since release date, played online for over a year before i modded in feb, so i would have 2 strikes but im banned i mite try getting on live again today just incase
i mite try getting on live again today just incase Im bored of halo3 already and plan on buying a seperate core system for playing shadowrun online, so I reFlashed my drive today ms28 with xtreme52 lets see how long it takes me to get banned.