Rumor: PartnerNet Bricking Kits?

Thing is this has little to do with MTWomg but the shit everyone has been doing to piss off Microsoft that I have been nagging about for the past... forever. This started happening imediately after the PN leaks and nothing is constant. For all we know they are just taking the missing kit's and knocking off anything unregistered.

PS: Assembler that is me

 

Only him and you know right... Your talking about the chineese site that leakes pnet shit. They had a poll up about the brickings when it frist started. You really think people don't know about that? I'd amagine you two would hang around a place like that. Makes sense why the chineese got hit first.

Btw Fuse blowing does not work by calling KeBlowFuses, or syscall 0x22 (HvxBlowFuses). You can take my word or not it's up to you.

 

TheFallen93, is correct on this statement. Also I don't blame microshit for doing this. A "ex" friend of mine sent me a link to this site that had most pnet content uploaded for leakers to download for jtag use. Like a long history of pnet games and content. Then that friend sent me to a "microsoft points generator" lol.

Yea, I think if JTAGGing never happened alot of microsoft mess wouldent have happened. So yeah...Fuck jtags...Fuck Leakers...Fuck MTW...

PS: <3 Gabe_K

 

Accessing hardware works by writing on hardware registers. Even if a machine lacks software to interface with a certain piece of it's hardware, it does not mean it can't be accessed/used.

So people assumed they were safe because the XDK kernel does not contain code to blow fuses they never expected this to happen.

Like I said already, a bunch of writes on the CPU registers are what cause fuses to be blown and as long a piece of code can gain hypervisor level of access it should be able to break havoc on an non modified XBOX360 system.

What if MS start to nuke JTAGs too ? People will try to sue them.
Then if MS start to use DMCA as shield for doing that ?

Then think a bit. That's why the JTAG tutorials recommend R6T3 removal.

Now, what will happen next ? :shrug:

 

I don't think MS can do the same to JTAGs, since legally those are people's property. Dev kits on the other hand belong to Microsoft, so they can do whatever they want with them.

 

so has anyone else been hit or is it just me and soniciso at the moment?

 

I was hit as well.

 

anyone up for some PSN?

 

You guys didn't happen to have any "homebrew" applications on your games library did you.. (This coming from MS)

 

i had xexmenu installed but only used it once (after i realised i could use neighborhhod to pull files off)

actually i ran the recovery again last week and wiped hard drive so it was not installed when it got nuked.

 

seriously? they are checking for homebrew applications in your game list now? give me a break with all the bullshit rumors flying around.

 

I didn't have any homebrew on my kit at the time it was killed. I had run SNES360 and some of my own homebrew in the past, but that's it. Did any studio kits get hit?

 

Bullshit rumors, coming from my Rep?

 

Its dumb because the people who created the original hombrew apps were actual developers from what I heard. Sooo redundant much?

 

Anywho.. That's all I could get from him, my kit is working fine.

 

Like the Xbox Live ban waves you can bet it will be all smoke and mirrors with lots of speculation but no fact.

Nuking kits based on whats in game list is exactly that. Devs from studios mess around with homebrew, did they get hit too?

 

To my knowledge, all the kits are fine in studio.. ( Also running the latest recoveries, however).. Also makes a difference, when MS want to know who's genuine.

 

I can understand maybe killing all kits running 9328.0, but my kit was on something more recent and still got hit. I imagine there are still plenty of legitimate kits out there that aren't on the latest recovery.

 

My home kit is at 9328.9.. Latest is 11427..
Gabe, what where you at?

 

I was on 9328.9.