Rumor: PartnerNet Bricking Kits?

Well you won't be fine for long.

 

How are you so sure?

 

Im sure Microsoft is taking missing MAC addresses and dealing with the issue.

 

ugh this is odd i just remember i removed the r6t3 on one of my xenons because i was messing with the KK exploit and yet it still died WTF?!

 

Possibly trying a combination of removing the resistor as well as a nand restore?

 

Doesn't matter... a shitload of Chinese people have been banned.

 

It belonged to a studio before, but it never connected to XePN until i recieved it.
over 16 poeple
yes
yes

You dont know that gabe, dont rain on my parade.

 

Sucks. Well Tyler, keep us updated, please.

 

pshhh im staying offline now for atleast a week,

i dont understand this though, how could they break the units remotly? i can see banning them, but breaking them seems a bit unethical.

just glad my precious didnt get hit.

Maybe they found out one of the main sellers, and found his schinlers list of dev serials and when on from there? dunno?

 

I thought it was common knowledge that MS could execute code remotely. Yes meaning that they can probably blow it up if they wanted.

 

then if thats the case they aren't remotely blowing fuses. Its gotta be something else

 

Maybe, maybe not. The resistor removal has never been confirmed to work on a dev kit, only retail.

 

If everyone didn't do stupid shit like I said this wouldn't happen. Post your RRoD error codes and if you have a nand dump contact me. Regaurdless of what Sonic-Iso says you might still want to remove the resistor anyway. As for it not being confirmed to work on Devkit's, the resistor is the only known component that can kill an efuse.

 

If anything, it makes more sense that xdk can "opt" out of fuse blowing, and that retails cannot.

You think they made a the retail revision with resistor removal in mind?

 

Good point.

Well, guess I'll be trying to remove my resistor, just in case.

 

The resistor has been proven to polarize the circuit which enables an voltage higher than the normal one which powers the CPU core. It's not the real supply which powers the fuse blowing engine, but more like an resistor that pull up the circuit which enables it. An XDK might contain an different set of components on that circuit, which could allow for an alternative "enable" for the fuse blowing logic.

I mean, an backup enable circuit for efuse blowing could exist ...

 

I don't doubt this.

 

error code 0022 all across the board >_

 

btw sondow... efuse blowing is NOT possible on devkits... lemme school you a bit. the HvxBlowFuses and KeBlowFuses are not complete on the devkit firmware. so nice try heh.

 

Things they could be doing:

Blowing the CB revocation fuse ... (this could be repaired with an updated version CB and I believe this is most likely what they're doing as in case they get the units back they can be repaired)

Changing the lockdown value (Could be fixed too like the #1)

Changing the 2 first fuse lines on a invialid value (not reversible)

Corrupting the CPU key... (not reversible)


Analysis of an bricked set would be interesting