Consumer waste devkits

I do what I wanna.
Edit.
Edit.
Edit

 

XENON AND I HAVE ACHEVD GRATENEZ :nod:

 

I am good, give me youuuuuuuuuur $$$,

Check those people, I dont know them and they say I AM GOOOD

 

On a real note, I was curious about if legal ownership was possible as far as being entitled to pursue the costs of damages caused by someone remotely bricking something that legally belonged to you.

Like with jtag's, very similar, you own the hardware but not the software or the networks they're used on. I haven't heard any credible reports of them being bricked by any kill switch.

 

I think you do legally own a consumer waste devkit. Once microsoft sends it out to be destroyed it is no longer their property.

 

Very incorrect. They own the copyright on the system and whatnot.
Same as when the police get rid of hard drives with confidentual material; it doesn't suddenly become 'oh they that get it own it'.

 

As far as that argument goes they own the copyright on a retail unit as well, the only difference I can see would be ownership of the hardware.

 

The difference lies in the agreements for using the online features and the software. Kits don't get bricked without going on ParterNET.

 

Yes they do.

 

nigga wat? I followed all the threads and news about the mass brick-waves and not once did I hear about anyone getting hit without connecting to PNET?

 

I Vote Obama

 

+ Company secrets.
Same as how the police raided engadget to get the prototype iphone 4.

 

No need to be a raging racist...

There are MULTIPLE ways to brick a kit...Not only by pnet, thus your statement is false.

 

tell me another way?

 

Dodgy recovery disks.

I'm pretty sure the so-called xbox police gave someone a bum recovery, or file, and bricked someones xbox ?

amiright ?

 

that can be recovered by reflashing

 

Oh really now?

 

If your R6T3 resistor is removed you can recover from a brick if you have a backup of your nand, or have the cpu key and keyvault.

As well, if a dodgy recovery disc is the only problem, that does not burn any fuses. So even if you don't have R6T3 removed, you should be fine.

Moral of the story: if you want to keep your devkit from being bricked, make a backup of your nand, find your cpu key if possible, and remove R6T3.

 

1) lolracism
2) I didn't mean to say there was only one way to do it, I was saying that's the only time that microsoft has actively struck back at so many grey-market XDKs at once. Now that I read my original post I guess it's easy to misinterpret that.

 

well, ive seen a lot of pnet stuff end up on torrent sites etc etc since the bricking/banning wave, not that I endorse the leaks but it makes me wonder if MS will be as willing to launch another attack against the grey market devs.