Rumor: PartnerNet Bricking Kits?

Well it does check the rsa. So for devs the payload is probally signed with the same private key as the bootloaders and kernel/hypervisor.

 

It seems to be executing files structured nearly the same as the bootloaders.

 

I've witnessed myself some odd situations with my original/non tampered retail XBOX360 console while I attempt to power it off and it engaged on a forced "background download" behavior without I having set it up for doing such. Network router had logs with outbound traffic of something around 18 megabytes for that period of time the unit was "off" but still running. I am sure my console was being "diagnosed" back then as they were looking for hacks and odd/suspicious stuff on security logs. If I notice something like that happening, I just let it run because I know my console is clean and I have nothing to hide.

They could do that while I am playing a game and I wouldn't notice at all. :lol:

My "educated guess" is that Microsoft is extremely upset with the piracy that has been affecting their platform and decided to use all the tools they had developed in the begging, when they developed the original specs for the system software.

I mean a lot of the stuff they're using now have been on the system since day1... An excellent way of keeping hackers clueless about how they're detecting hacks is keeping the detection code out of the system software (which can be audited by anyone who can decrypt and disassemble/reverse engineer it) and deliver such code while the system is on line. It won't leave leftovers if it's ran only on RAM. Also they are very likely deciding which consoles are tested on a semi-random basis which makes getting samples of such code extremely difficult.

So, the function that allows them to "escalate" privileges for uploaded payloads was likely added to allow them to scrutinize supposedly hacked units and be a step ahead the hackers.

I would blame it's existence on how hackers exploited and hacked the classic XBOX. There's aways losers and idiots who take hacked consoles to the retail online service and try to make fun of the legitimate customers who paid for their games.

I remember an interview years ago (By the time the King Kong Exploit surfaced) with the engineer who developed the security for the XBOX360 and he kind of mentioned something about having some "dormant security mechanisms" they could use anytime if they needed. Perhaps was this "Xe/HvxKeysExecute" mechanism what he meant...

Anyway, since it requires a piece of code secured with the bootloader private keys, it's twice the security than what you would have on a normal XEX file.

For the people who lose devkits, I know this isn't funny so I'm sorry about you guys ...

And stay away from stuff you shouldn't be tinkering with on first place.

 

I just keep getting in more reports of dead kits and people keep asking me why its happening... oh the irony.

 

Irony?

 

Yeah Forza 2 beta comes to mind.

 

Yeah, that's when you don't know what the definition of irony is.
However, I'd like to point out that the code mentioned by soniciso doesn't match with the error he mentioned before.
0022 or 0020 would happen in 2BL/3BL

 

0022 (E10) happens on systems with blacklisted CB if the owner flashes the older image with the old blacklisted CB back so ...

Don't you think it's possible that they're just blowing the CB revocation fuse like I mentioned earlier ?

And that error code (0x93) looks similar enough to what robinsod got when he were working on the timing attack (0x96).

At the time most of us had no idea that the CB even had an revocation mechanism.

robinsod listed the POST codes at the test point on a retail box at that time:

After he tinkered with the CB encryption and hash (Pairing data ?) he got this:

Original source : http://www.xboxhacker.org/index.php?topic=8221.0 (requires an account at the site)

 

I wish people would actually tell from facts they have confirmed [themselves] instead of hear-say...

0x1D is when 2BL's signature is verified... resulting with 0x96 when it fails.

 

Really? Because I'm pretty sure it has to do with the Partnernet leaks and people doing ignorant things on Microsoft's own private server... Yeah i'm pretty sure thats the one that comes to mind versus the idea of some random game that has nothing to do with microsoft once so ever being released years after it became extinct....

 

Sorry about that. For some reason I thought this was a first party title.

 

Not a problem.

 

> implying it wasn't a first party title that M$ obviously cares about

 

I think you misunderstood what he was saying. He wasn't being sarcastic in other words its a prototype of a game that was released in 2007 that has no ties to Microsoft.

 

+1

 

Forza 2 has "nothing to do with Microsoft?"

You can say that with a straight face? Seriously?

You publically leaked a dev build of a first party, internally developed title right after the JTAG hack hit and you don't think that Microsoft noticed? Guess what? They did.

I already mentioned it earlier in this thread, so don't need to rehash the details, but leaks of dev versions of full titles rate a lot higher on the internal alarm than an arcade leak.

-hl178

 

Yeah your completely right hl718 you always are. A game released 3 years ago that has a debug menu in it which I released a year ago and is no longer a microsoft exclusive is what caused this not the recent leaks in partnernet material and security that I have been warning everyone for months about which so happens to result in a recent retaliation. Yep I caused it.

 

Simply put, you're a hypocrite. You gotta stop acting like you know why Microsoft did this, since you don't. That's just it.

 

Because we became a threat. Obvious to anyone who has a brain.

 

lmfao guys this isnt shadowlags fault. im pretty sure the chinese with their jsteam crap had something to do with it.