Partnernet Safety Precautions [IMPORTANT]

As everyone can see from the recent events Microsoft appears to be fighting back (like I didn't see this coming). Anyway we will cut to the chase.
Keep your devkit's ethernet connection removed, any outside packets can be used to brick your kit if you MUST use your ethernet cord for transfering data and you do not own a external hard drive then you must do the following.

- Go into launcher tools > Network Settings > Game Network Configuration > IP Settings. Write down the IP Address.

- Disconnect the ethernet cord and backup your Hard drive to your PC

- Insert the recovery disc you are on and run it from your disc tray with Hard Drive attached. This will give you a new clean Nand and a Formatted HDD

- Enter in your Xbox 360 name and go to launcher tools > Network Settings > Game Network Configuration > IP Settings set it to Manual and input the IP you wrote down leaving the rest blank.

- Go to launcher tools > Network Settings > Game Network Configuration > DNS Servers set it to Manual leaving the fields blank

- Go to launcher tools > Network Settings > Debug Network Configuration and set it to Manual putting in the same IP as before but adding +1 to the IP (example: 192.168.1.10 / 192.168.1.11)
leave the rest blank (MAC Address won't be blank)

- Connect your network cable and test your PN connection, if it does not connect then that is good and you should be able to connect to neighborhood through your router.

This can not 100% garantee your safety but it should keep your devkit from accessing outside your home network.

Bearkiller's backup did not work and we are only assuming they are blowing efuses if this is the case then there is no restoring your development kit from this if this "rumor" is infact true. The code he recieved was 0022 which is GPU overheation. This could be a coincidence but just to be safe atm. Another precaution would be to desolder R6T3 resistor this resistor is used to blow efuse's but be warned this has not been tested on a development kit so results are unkown but if any negative results were to occur it should be fixed by simply resoldering it. If the Efuse theory is correct this should be the end all save all solution for development kits.

Most of all DO NOT under any circumstances leak anything, if it is infact true Microsoft is hunting down and destroying kits it is most likely due to this cause and note that all packages leaked from PN/XBL have your console ID tied to it.

 

as an alternative (what ive been doing)
just plug it directly into your computer via Ethernet
that works for us lazy folk

 

This works if you have multiple Ethernet ports, a lot of people do not.

 

Yeah that's exactly what I'm doing.. Now to just disable internet sharing.

 

Ok I decided to sticky this thread temporarily until this whole thing calms down.

 

This is ridiculous.. No further comment.

 

Just dont go on Pnet, problem solved?

 

that is what I am thinking..do you have to connect to PN to get your kit bricked?

 

If you have access to an outside network your kit can be bricked remotely from the claims given. There is no pinpointing of the exact cause so no this isn't rediculous but its your kits and your risk so do as you please.

 

Changing you IP address doesn't save your kit in the first place, because that's not your identity. If anyone wants to brick your kit he'll be using your MAC address so no point to change IP address.
Second if you have proper setting in your network NO ONE can access your kit without hacking your network first.
Last if you don't want to anyone access your network just unplug you router from internet for the while when you play with your kit or put your kit in DMZ (demilitarized zone)

 

If you read the instructions its not changing your ip its keeping your ip active while disabling outside network access. In essesense your kit can only be accessed by your home network. I am aware of the possible ways they are destroying kits but that can't happen if they can't send or recieve packets from your kit.
Second if you can connect to PN Microsoft can access your kit.

 

Thanks! This is all i needed to know! I am not taking any chances until we find out what is causing this.

 

Check my post for the stats of remote brick in China:

http://www.assemblergames.com/forums/showpost.php?p=415658&postcount=169

 

Thanks for the contribution.

 

Sorry, i want to translate this post in french for french website but i don't know what is a "Bearkiller's backup". Can you explain please ?
Thanks.

 

lmao

 

Hes referring to a user here named bearkiller, and he was talking about his nand back up.

Hawk

 

Lol, thanks for info. ^^

 

I simply plugged in my XDK's Mac addresses and IPs to an Internet Access Policy on my router. Works fine on internal network, but has no way to access the internet.

100x easier than doing all this recovery crap ._.

-Doom

 

1. Not everyone has your type or router with those settings...
2. The recovery is to clean the nand incase the killer is a sleeper
3. This isn't "crap"