|
how ms detects modified 360
|
|
Senior Member
|
15. November 2009 @ 20:35 |
Link to this message
|
Originally posted by John_Donn:
Originally posted by andmill11:
Originally posted by azzidrain:
Then why don't you know jack...
Excuse me? I have not posted a single time in this thread before this.
r u retarded yes you did 2 above this post. you told him we dont need your silly links, what a dumbass
I had a reply. But I edited it. If he can't understand what I was saying then that is his own problem.
Anyways, we are now way off topic. I am done with this topic.
This message has been edited since posting. Last time this message was edited on 15. November 2009 @ 20:41
|
|
Advertisement
|
|
|
|
|
Kenny25
Junior Member
|
15. November 2009 @ 23:29 |
Link to this message
|
|
Why is everyone fighting lol..BACK ON TOPIC. I don't know of any more ways MS can detect. Besides poorly stealthed backups, and possible..doubtful but possibly a fault in the AGBX program. I've been flashed for about 2 weeks, and only played 2 backups and I have not been banned yet.
|
Senior Member
1 product review
|
16. November 2009 @ 02:20 |
Link to this message
|
it can't be bad rips that are getting people banned, c4e even said himself that he has a system that never played a game and it got banned. His system that was updated and then flashed hasn't been banned so it leads me to think that if you were modded when the update rolled around it triggered something in the drive and that sent the red flag to microsoft and that is what is causing the bans.
|
Member
|
16. November 2009 @ 04:17 |
Link to this message
|
Originally posted by mikeismad:
it can't be bad rips that are getting people banned, c4e even said himself that he has a system that never played a game and it got banned. His system that was updated and then flashed hasn't been banned so it leads me to think that if you were modded when the update rolled around it triggered something in the drive and that sent the red flag to microsoft and that is what is causing the bans.
hmm... interesting theory here. my roomate had a box that was modded and it was over 4 years old. i flashed it with 1.51 and when i plugged it in it was hit. Now, we didnt have the XBL on that console for a few weeks because we were just playing UFC against each other. furthermore, after he got hit i found out there was 1.61 for my drive and i flashed it with JF and its own psu. I have played all the same games in my box as he did but i played a different copy of MW2 that was autofixed level 3 with abgx. I played one day and then got hit. so maybe they can sense the change in f/w. anyone else hit right after they upgraded to play wave 3 games? what about wave 4 games? anyone still on XBL that has not updated their f/w? maybe these questions could eliminate the theroy above or support it.... just my $0.02
|
|
qwert99
Senior Member
|
16. November 2009 @ 10:43 |
Link to this message
|
Originally posted by mikeismad:
it can't be bad rips that are getting people banned, c4e even said himself that he has a system that never played a game and it got banned. His system that was updated and then flashed hasn't been banned so it leads me to think that if you were modded when the update rolled around it triggered something in the drive and that sent the red flag to microsoft and that is what is causing the bans.
I must have missed this. The last I had heard, C4Eva still hadn't given an update on the ban status of his test boxes.
Can you link me, please?
$38 on new discs -- Check
$15 on burn after burn that showed as a DVD -- Check
$11 on new laser -- Check
$28 on new multimeter -- Check
___________________________________
Knowledge from Leerage? -- Priceless
|
|
MReprogle
Member
|
16. November 2009 @ 14:07 |
Link to this message
|
Originally posted by qwert99:
Originally posted by mikeismad:
it can't be bad rips that are getting people banned, c4e even said himself that he has a system that never played a game and it got banned. His system that was updated and then flashed hasn't been banned so it leads me to think that if you were modded when the update rolled around it triggered something in the drive and that sent the red flag to microsoft and that is what is causing the bans.
I must have missed this. The last I had heard, C4Eva still hadn't given an update on the ban status of his test boxes.
Can you link me, please?
Yeah, I hadn't heard anything of these tests being complete. I'd love to know, even it is the firmware. C4Eva is still awesome, and the fact that we were able to get away with it for so long is a true testament.
|
Senior Member
|
16. November 2009 @ 14:47 |
Link to this message
|
hey guys this is from the site Logic Sunrise which is a french site and i had translated to english. some words are still broken but you can make it out.
"Additional information on the Ban Dear all,
As everyone knows, this latest wave of ban is particularly deadly and is even likened to a tsunami lol.
As a reminder, here are the main reasons for banning the xbox-live:
- Play a game NOT stealth (Online or offline, with or without hard drive / memory card)
- Play a game before its official release. (online or offline, with or without hard drive / memory card)
- Playing a PRE-RELEASE (Even after its official release. Avoid thus release available 2 weeks before the release of the game online or offline, with or without hard drive / memory card)
What makes this new wave of ban is particularly virulent lies in two points.
The first is that playing a game before its official release is also subject to the ban with the originals. Many people who bought MW2 Saturday when the sale was prohibited until Tuesday (Monday evening for Virgin and Fnac in the evening MW2) were banned because of that.
The second point is not insignificant: the iXtreme firmware is partially detectable.
What you should know is a perfect stealth backup, is a priori not distinguishable from an original. So for m $ if the previous points have been respected, they do not they still have much to banish you, only "detect" the firmware.
The firmware is not detectable, because not dumpable by the console (at least for Liteon). Detection is much more vicious.
Indeed, like KREON firmware, firmware iXtreme sometimes errors (Example: Angle Value Read Error on SS). And then sometimes return the wrong information to the console, and this is how that $ m detects that a player is flashed or not.
The positive point is that these errors are not systematic. Why we specify that the firmware of the player is "in part" detectable. You can very well play for 2 hours at your favorite game (in backup or original) without these errors occur and the console detects.
Therefore here is our advice:
Systematically record your games on the hard drive before playing. Thus, you minimize the chances of being banned, since the only time where mistakes can be obtained not have the time to authenticate the disc before launching from the disk drive.
This is NOT a panacea to avoid being banned, but in this respect in addition to all the others, you decrease your chances of being banned.
A bientot"
If you send me questions on Live about modding or anything related i will block you. Dont be an idiot.
|
|
gameover9
Suspended permanently
|
16. November 2009 @ 15:19 |
Link to this message
|
|
Problem with LT will be ABGX. One bad rip could ban you and you'd never know which one it was.
|
|
mraccoe
Newbie
|
16. November 2009 @ 15:20 |
Link to this message
|
Originally posted by 561427:
Originally posted by mikeismad:
it can't be bad rips that are getting people banned, c4e even said himself that he has a system that never played a game and it got banned. His system that was updated and then flashed hasn't been banned so it leads me to think that if you were modded when the update rolled around it triggered something in the drive and that sent the red flag to microsoft and that is what is causing the bans.
hmm... interesting theory here. my roomate had a box that was modded and it was over 4 years old. i flashed it with 1.51 and when i plugged it in it was hit. Now, we didnt have the XBL on that console for a few weeks because we were just playing UFC against each other. furthermore, after he got hit i found out there was 1.61 for my drive and i flashed it with JF and its own psu. I have played all the same games in my box as he did but i played a different copy of MW2 that was autofixed level 3 with abgx. I played one day and then got hit. so maybe they can sense the change in f/w. anyone else hit right after they upgraded to play wave 3 games? what about wave 4 games? anyone still on XBL that has not updated their f/w? maybe these questions could eliminate the theroy above or support it.... just my $0.02
I had 3 boxes originally modded by the same guy. All 3 Lite-on, one spoofed to a BenQ.
We took 1 of the Lite-on drives and got it flashed to 1.6 back in June. It was the first one of the 3 to get banned. I recently took the other two to get flashed to 1.61 (Benq) and 1.6 (Lite-on)...
The BenQ was instantly banned as soon as I hooked up to Live. It was not banned the night before it was updated. It could be a coincidence and I was going to be banned anyway, but I never got around to connecting to LIVE the day I was banned before the update.
The Lite-on is an interesting case. Updated the firmware last Wednesday, tested it Wednesday, tested it Thursday, no Ban. Didn't even play a game, just connected to LIVE. Tested it again Friday with a disc in the drive and was banned.
I don't know if that helps, but just trying to supply some more info.
This message has been edited since posting. Last time this message was edited on 16. November 2009 @ 15:24
|
|
gameover9
Suspended permanently
|
16. November 2009 @ 15:39 |
Link to this message
|
|
what game did you put in the drive?
|
|
gradeon
Junior Member
|
16. November 2009 @ 15:43 |
Link to this message
|
|
people have to stop putting their faith in abgx that thing is crap.
|
|
gameover9
Suspended permanently
|
16. November 2009 @ 15:46 |
Link to this message
|
Originally posted by gradeon:
people have to stop putting their faith in abgx that thing is crap.
crap? Too bad you need it or you will be banned for sure!
|
Senior Member
|
16. November 2009 @ 15:46 |
Link to this message
|
Originally posted by gradeon:
people have to stop putting their faith in abgx that thing is crap.
its not crap,, the people that use it incorrectly are the crap besdies what else is there? ...nothing mulleter has been dead for over a year
If you send me questions on Live about modding or anything related i will block you. Dont be an idiot.
|
|
mraccoe
Newbie
|
16. November 2009 @ 15:49 |
Link to this message
|
Originally posted by gameover9:
what game did you put in the drive?
I believe it was Borderlands or MW2. Both original rips using Kreon FW.
|
|
gameover9
Suspended permanently
|
16. November 2009 @ 15:49 |
Link to this message
|
Originally posted by mraccoe:
Originally posted by gameover9:
what game did you put in the drive?
I believe it was Borderlands or MW2. Both original rips using Kreon FW.
Well Borderlands had a bad rip floating around and MW2 is known to get you banned so there you go.
|
|
mraccoe
Newbie
|
16. November 2009 @ 16:07 |
Link to this message
|
Originally posted by gameover9:
Originally posted by mraccoe:
Originally posted by gameover9:
what game did you put in the drive?
I believe it was Borderlands or MW2. Both original rips using Kreon FW.
Well Borderlands had a bad rip floating around and MW2 is known to get you banned so there you go.
Well I rip all my games myself from retail discs. But now I see another thread on here about KREON's not being safe anymore... my best guess is that one of my Kreon rips (most likely MW2) is what did us in.
|
Member
|
16. November 2009 @ 17:22 |
Link to this message
|
it would be worth while to get an xbox 360 and then flash it with the newest frimware right now in the middle of the ban wave and then before playing it at all flash it back and wait. that way we can control more of the variables in the equation. find a box, flash it, then immediatley revert it back ya know? that way if it DOES happen to get banned, even after it has been flashed backed to stock, we could perhaps find out if m$ can detect changes among the firmware.
anyone picking up what im putting down? smell what i'm stepping in?
|
|
dgrandt
Newbie
|
16. November 2009 @ 20:12 |
Link to this message
|
Originally posted by 561427:
it would be worth while to get an xbox 360 and then flash it with the newest frimware right now in the middle of the ban wave and then before playing it at all flash it back and wait. that way we can control more of the variables in the equation. find a box, flash it, then immediatley revert it back ya know? that way if it DOES happen to get banned, even after it has been flashed backed to stock, we could perhaps find out if m$ can detect changes among the firmware.
anyone picking up what im putting down? smell what i'm stepping in?
How's about gettin a new console, accepting the latest updates - install games to HDD from retail discs (accepting latest updates) - then flashing with the latest IX FW, and then using nothing but backup copies of those same retail discs to load up the games and play from the HDD. Now if THAT box gets banned... omigosh, omigosh.
|
|
Aiur
Member
|
16. November 2009 @ 21:54 |
Link to this message
|
Originally posted by dgrandt:
How's about gettin a new console, accepting the latest updates - install games to HDD from retail discs (accepting latest updates) - then flashing with the latest IX FW, and then using nothing but backup copies of those same retail discs to load up the games and play from the HDD. Now if THAT box gets banned... omigosh, omigosh.
Or you could simplify the process and get a cheap, used 360, flash it with the latest firmware, leave it connected to the internet and turn it on once a day (downloading any updates), and see if it gets banned or not. If it gets banned, then you definitely know the firmware is detectable. I may do this myself, so if I decide to do it I will let the board know the results.
|
Member
|
16. November 2009 @ 23:35 |
Link to this message
|
Originally posted by Aiur:
Originally posted by dgrandt:
How's about gettin a new console, accepting the latest updates - install games to HDD from retail discs (accepting latest updates) - then flashing with the latest IX FW, and then using nothing but backup copies of those same retail discs to load up the games and play from the HDD. Now if THAT box gets banned... omigosh, omigosh.
Or you could simplify the process and get a cheap, used 360, flash it with the latest firmware, leave it connected to the internet and turn it on once a day (downloading any updates), and see if it gets banned or not. If it gets banned, then you definitely know the firmware is detectable. I may do this myself, so if I decide to do it I will let the board know the results.
actually i thought about it when i posted this message. the point is to control the variables here. if we have a virgin box and then flash it the very first time we turn it on and then play ONLY legit games with it, then we KNOW for sure that the firmware is being seen by m$ and they aren't liking something about it and then banning us. next we can do the same and introduce games that are installed to the hard drive via originals but played with backups in the tray. just methodical in our research and testing. but research always costs money. maybe have one of the established members who is trusted by the community accept donations and then perform the tests and post his write-ups including as MANY details as possible (IE how box was flashed, what drive and mobo it was, what f/w was used, blah blah blah ya know just meticulous details). I remember there was a big deal about flashing the new lite-on and when someone found out hoe to decrypt keys he decided to charge 40 bucks or something like that. well the community came together and beat him at his own game by decrypting the code, and using his service to confirm the key that they made up; thus confirming their decryption... this is like that. NOW LETS GET OUT THERE! oorah!!! hahaha
This message has been edited since posting. Last time this message was edited on 16. November 2009 @ 23:48
|
Senior Member
1 product review
|
17. November 2009 @ 02:16 |
Link to this message
|
Originally posted by qwert99:
Originally posted by mikeismad:
it can't be bad rips that are getting people banned, c4e even said himself that he has a system that never played a game and it got banned. His system that was updated and then flashed hasn't been banned so it leads me to think that if you were modded when the update rolled around it triggered something in the drive and that sent the red flag to microsoft and that is what is causing the bans.
I must have missed this. The last I had heard, C4Eva still hadn't given an update on the ban status of his test boxes.
Can you link me, please?
Sorry it wasn't C4E it was team xecutor whic is still a pretty trust worthy source. Link is below. I fully believe that if you are on stock firmware when you update you should be pretty safe.
http://team-xecuter.com/xbox-live-some-test-results/
|
|
tommytoes
Newbie
|
17. November 2009 @ 02:35 |
Link to this message
|
Originally posted by mikeismad:
Originally posted by qwert99:
Originally posted by mikeismad:
it can't be bad rips that are getting people banned, c4e even said himself that he has a system that never played a game and it got banned. His system that was updated and then flashed hasn't been banned so it leads me to think that if you were modded when the update rolled around it triggered something in the drive and that sent the red flag to microsoft and that is what is causing the bans.
I must have missed this. The last I had heard, C4Eva still hadn't given an update on the ban status of his test boxes.
Can you link me, please?
Sorry it wasn't C4E it was team xecutor whic is still a pretty trust worthy source. Link is below. I fully believe that if you are on stock firmware when you update you should be pretty safe.
http://team-xecuter.com/xbox-live-some-test-results/
I came across this too. I would still give it a week or two and see if they are still kicking. 4 systems isn't a very thorough test when people are still playing online with mods everyday since bans (although I know of none personally).
|
|
tcs614
Junior Member
|
17. November 2009 @ 02:44 |
Link to this message
|
If microsoft is reading the firmware of our modded drives then banning us then someone please explain this to me. I had a friends xbox that got the rrod several months before this ban wave. I was getting it prepared to be sent in by putting the xclamps back in cause i fixed it before and I didnt want microsoft to think my warranty sticker was bullshit cause obviously i would have had to be inside the box in the first place to to apply the fix. So after i put the xclamps back in it started working again for some reason. Knowing that all these bans were going on I switched the firmware of his drive back to the original (I flashed his benq drive a while back to 1.4 then it broke on him). When I tried to get onto live I got the ban message right away. I got the original firmware from an ixtreme package and made sure it wasn't patched with ixtreme by using firmware toolbox.
This message has been edited since posting. Last time this message was edited on 17. November 2009 @ 02:46
|
|
scum101
Suspended due to non-functional email address
|
17. November 2009 @ 03:11 |
Link to this message
|
|
Think about it guys... boxes which have been repaired by M$ and never modded have been banned.. BUT .. because the console serial number appears in the M$ repairs database they have been able to get them unbanned.. now doesn't that tell you all something?
|
|
Advertisement
|
|
|
|
tommytoes
Newbie
|
17. November 2009 @ 03:13 |
Link to this message
|
Originally posted by tcs614:
If microsoft is reading the firmware of our modded drives then banning us then someone please explain this to me. I had a friends xbox that got the rrod several months before this ban wave. I was getting it prepared to be sent in by putting the xclamps back in cause i fixed it before and I didnt want microsoft to think my warranty sticker was bullshit cause obviously i would have had to be inside the box in the first place to to apply the fix. So after i put the xclamps back in it started working again for some reason. Knowing that all these bans were going on I switched the firmware of his drive back to the original (I flashed his benq drive a while back to 1.4 then it broke on him). When I tried to get onto live I got the ban message right away. I got the original firmware from an ixtreme package and made sure it wasn't patched with ixtreme by using firmware toolbox.
There are a lot of theories floating around. Some think that stealth checks can be detected in the new firmware. If you have ever played a bad rip it is stored and sent in to be evaluated (think send/don't send errors in windows).
Quote:
Indeed, like KREON firmware, firmware iXtreme sometimes errors (Example: Angle Value Read Error on SS). And then sometimes return the wrong information to the console, and this is how that $ m detects that a player is flashed or not.
Scroll up and check out stealthdf's post on this page. A lot of thoughtful ideas that he was nice enough to rough translate. As it stands anything known to be definitively detectable isn't being released yet by either side.
|
