People selling kits were knowingly selling stolen goods. Every single one of them was also selling pirated software. So the hands were most certainly not clean. A more apt analogy would be sellers offering up keys to a grocery store to a group of starving homeless and telling them "here, you can look, but not touch" with a wink and a nod. Yes, people should take responsibility for their actions, but that means ALL. If the sellers of kits really just wanted to dev for themselves they never would have sold openly on public boards and they never would have posted publically about what they were doing. The sellers were the original source of the leaked kits and they were sold for monetary gain. It's a simple equation and it's one that inevitably lead to a hole being plugged. After all, if all sellers cared more about the integrity of the network than profit kits would have either never been sold, or only sold to people who signed strict NDAs. -hl718
So of all the kits that got messed up was there a common source? Maybe they just found out the main suppliers? And just looked at how they where getting kits. Hawk
You may be right but the point of this manhunt is because we became a threat. I might also point out this entire board is used to trade rare goods and collection hardware. Now if people didn't start acting insane then it wouldn't happen and your analogy I am going to have to strongly disagree with no one is starving here. People were sold kits to collect them and use them to develope software not be used to leak shit off Partnernet and endanger everyone and yet again I fall on deaf ears.
i hear its only kits 05-07 (YTD) maybe its Microsoft's way of phazing out older models to protect its IP's?
That is a false rumor. Not to mention doing anything of the sort to retail kits would be highly illegal. -hl718
Like I said before they are most likely banning missing kits. It also isn't hard to get someone's console ID from leaked packages either.
I know alot of people with kits, some of them on MTW's friend list, most of them played on pnet, none of them have been hit is all im saying. They have been on the few days, some are on right now.
K. 0022 is the exact error code as all other kits hit with this. It's not your average hardware failure.
Faults from genuine hardware failure would be "0020" (CPU didn't start at all) or "0102" (RAM fault) or "0110" (GPU fault ?)... "0022" means the CPU started but gave up from booting at the CB for some reason. CB revocation is an excellent way to make an system stop working and cause it to return an "0022" error code. But then there's 768 fuses on the CPU and they can blow anyone which aren't blown yet. Fun stuff. Blowing them all is possible, and I suppose it would cause the system to error out "0022" too...
They will be hit. Reports of bricks started on the 24th, I was online many times between the the 24th and yesterday, when I got hit.