|
Upgraded to 250Gb Hard Drive
|
|
|
manu07
Member
|
26. October 2009 @ 20:22 |
Link to this message
|
Should i wait till the release of modern warfare 2? to connect to xbox live. Is it a possible ban issue?
This message has been edited since posting. Last time this message was edited on 26. October 2009 @ 22:27
|
|
Advertisement
|
|
|
|
|
coorva
Suspended due to non-functional email address
|
26. October 2009 @ 22:46 |
Link to this message
|
Originally posted by manu07:
Should i wait till the release of modern warfare 2? to connect to xbox live. Is it a possible ban issue?
???????
|
|
manu07
Member
|
26. October 2009 @ 22:53 |
Link to this message
|
Originally posted by coorva:
Originally posted by manu07:
Should i wait till the release of modern warfare 2? to connect to xbox live. Is it a possible ban issue?
???????
let my be more specific i upgraded my hard drive to a 250gb. Now from what i have read these hard drives are only bieng released as a bundle with modern warfare 2 consoles. and that release date is nov 10 so is it safe to go on live before that date with this hd?
|
|
coorva
Suspended due to non-functional email address
|
26. October 2009 @ 22:56 |
Link to this message
|
Originally posted by manu07:
Originally posted by coorva:
Originally posted by manu07:
Should i wait till the release of modern warfare 2? to connect to xbox live. Is it a possible ban issue?
???????
let my be more specific i upgraded my hard drive to a 250gb. Now from what i have read these hard drives are only bieng released as a bundle with modern warfare 2 consoles. and that release date is nov 10 so is it safe to go on live before that date with this hd?
i would say no,,
|
AfterDawn Addict
|
27. October 2009 @ 09:21 |
Link to this message
|
|
it's up to you.
Hard drives aren't a big issue to MS like games are.
There are plenty of people modding the hard drive now, so why not do it?
need jtag help? Xbox 360 console repair? PM me or chat |
|
John_Donn
Member
|
27. October 2009 @ 09:49 |
Link to this message
|
|
I have never heard of a hard drive causing a ban. Plus it is possible to buy the 250gb harddrive from overseas now if you are in America. For all they know that is what you did. I would say your def. ok
|
Member
|
27. October 2009 @ 10:45 |
Link to this message
|
Where did you get the file to upgrade your HD to 250GB? You used HDD Hacker correct?
|
|
qwert99
Senior Member
|
27. October 2009 @ 11:03 |
Link to this message
|
Originally posted by John_Donn:
I have never heard of a hard drive causing a ban. Plus it is possible to buy the 250gb harddrive from overseas now if you are in America. For all they know that is what you did. I would say your def. ok
I've never heard of memory cards being remotely disabled, either.... until this past week.
The situation is slightly different for the memory cards, since there is an organized commercial company making money specifically off those cards without paying MS their due, and also since those cards use a specific proprietary feature. However, it certainly made me rethink the matter a bit.
Worst case scenario, at least MS has shown that they are open to 'just' (ha) disabling the devices from working and not all-out banning. If nothing else, and MS does disable all 'non-official' (gimme a break) HDDs, you still have a 250GB HDD that you can use elsewhere.
Still though, modded HDDs seem pretty easily detectable, and it has got at least this guy nervous about the upgrade. Nervous enough to never do it? Probably not. Nervous enough to give it another month or two? Probably so.
|
|
manu07
Member
|
27. October 2009 @ 12:20 |
Link to this message
|
|
what would prob be a better idea is getting a hddss.bin from another source like a friend or buy one. Return the drive after u get the hdss.bin, and at least that way there are much fewer hds with the same serial info
|
|
manu07
Member
|
27. October 2009 @ 12:23 |
Link to this message
|
i also noticed when i was flashing that the hddss.bin was originaly from a hitachi drive or toshiba, i cannot remember and the drive i flashed it too was a wd bev series. i wonder if this can also be a way of getting detected?
|
|
qwert99
Senior Member
|
27. October 2009 @ 12:24 |
Link to this message
|
Originally posted by manu07:
what would prob be a better idea is getting a hddss.bin from another source like a friend or buy one. Return the drive after u get the hdss.bin, and at least that way there are much fewer hds with the same serial info
My thoughts exactly. A unique HDDSS would definitely go a long way towards protecting these drives from being able to be detected.
In a perfect world, some keygen maker somewhere would get a bunch of unique HDDSS serials and crack the algorithm for them so that essentially infinite new codes could be generated randomly. There would still be ways for MS to detect that, but at least it would be much more difficult for them.
|
|
qwert99
Senior Member
|
27. October 2009 @ 12:26 |
Link to this message
|
Originally posted by manu07:
what would prob be a better idea is getting a hddss.bin from another source like a friend or buy one. Return the drive after u get the hdss.bin, and at least that way there are much fewer hds with the same serial info
My thoughts exactly. A unique HDDSS would definitely go a long way towards protecting these drives from being able to be detected.
In a perfect world, some keygen maker somewhere would get a bunch of unique HDDSS serials and crack the algorithm for them so that essentially infinite new codes could be generated randomly. There would still be ways for MS to detect that, but at least it would be much more difficult for them.
Originally posted by manu07:
i also noticed when i was flashing that the hddss.bin was originaly from a hitachi drive or toshiba, i cannot remember and the drive i flashed it too was a wd bev series. i wonder if this can also be a way of getting detected?
Unless MS goes to extreme measures, the drive can only report what it knows about itself. The only thing the drive knows about itself is what is contained in those files. So even if it is a WD, if it thinks it is a Hitachi or Toshiba due to those modded files, that's what it will report.
I think the weak link here is so many people sharing the same serial number info on the hard drives, like you say.
This message has been edited since posting. Last time this message was edited on 27. October 2009 @ 12:29
|
|
manu07
Member
|
27. October 2009 @ 12:34 |
Link to this message
|
|
true it might just be wiser to wait then and get my unique hddss.bin
|
|
qwert99
Senior Member
|
27. October 2009 @ 12:40 |
Link to this message
|
Originally posted by manu07:
true it might just be wiser to wait then and get my unique hddss.bin
Yeah, I think that's smart. Even if you shared the serial with a group of friends, it'd be a heckuva lot better than sharing it with the whole internet.
Then again, if MS does ever disable modded HDDs, we can always take action after the fact. That way, if MS never does anything about it, we won't have to go through the trouble.
|
|
John_Donn
Member
|
27. October 2009 @ 13:25 |
Link to this message
|
|
Yea the unique SS. numbers will def help but still 2 is one more than "legal" so I would think ANY duplicate would cause the disabling.....
|
|
Advertisement
|
|
|
|
qwert99
Senior Member
|
27. October 2009 @ 18:40 |
Link to this message
|
Originally posted by John_Donn:
Yea the unique SS. numbers will def help but still 2 is one more than "legal" so I would think ANY duplicate would cause the disabling.....
Yes, that is possible
It depends on how MS chooses to verify the authenticity of the hard drives, if they ever choose to.
They have two options, as I see it:
1.) Compare each serial on the hard drive against a database that is constantly kept up to date with the newest hard drive serial numbers that have actually been manufactured. Then check against the DB to ensure that each serial has not been used more than once. This would be pretty difficult, time-consuming, and expensive.
2.) Compare each serial to a list of known "bad" serials -- eg, hddss files "out in the wild". In addition, check each serial against an algorithm (aka a math formula) to determine if the serial is legit (the 360 itself may already do this). Much faster, cheaper, and easier.
If MS chose to use option #1 to verify serials, everybody is screwed.
If they choose to use option #2, anybody who used a 'default' hddss file available on the web is screwed, but if somebody were to get a non-public serial, even if it is used more than once, they should be okay. In addition, if somebody were to crack the algorithm on how the serial is calculated, they could generate their own unique, random serial number that seems to be legit, even though it may never have been assigned to an actual hard drive.
|
