Rumor: PartnerNet Bricking Kits?

Hello,

Bugess meant, he attached a nand dump from a demo kit brick via XePartnerNet.

Bye

 

yes, sorry:shrug:, it's a brick through PartnerNet

 

Just saw an 05 Xenon get bricked before my eyes, so it's still happening.

Careful where you tread ;o

-Doom

 

thanks doom

 

iTread

 

Mh thought that they only bann the last time. But ok, good to know.

 

godd dammit!
thanks for the heads up i was about to go on lol....

 

Just some additional info, that it wasn't definitly not related to PTag/Friends List/Account. It was on a completely new tag with all the others long deleted and the kit hadn't been on since before the brickings started.

RROD after reboot, error 0022

-Doom

 

Honestly that bricks sure smell like boot-loader revocation, as I mentioned earlier on this thread.

 

yep, i mentioned this too and got called BS on it. I know someone who was banned doing a simple test to pnet from XDK tools, no profile loaded with a clean HDD. Rebooted to 0022

 

Which is very easy to do on a console-by-console basis when you have a serial blacklist.

As for bugess, unless you have the CPU key to decode that NAND image it's not going to be terribly useful.

-hl718

 

yes, no doubt its a serial blacklist. Any other theory is just scaretactics and confusion

 

Hmm actually the kit doom just saw get hit, I have the cpu key for... Ill ask for a dump

 

I asked, there's no before dump :|

And probably won't be an after dump either, lol.

-Doom

 

Somebody get a wee bit peeved and take out their frustrations on the console?

-hl718

 

So it is without a doubt serial black listing, and you can confirm this 100% true?

 

I have several dumps and also cpu-key. No luck with flashing
before dumps. I also tested to edit the LDV with 360flashtool,
but at the moment it can't handle my zepyhr dumb. Crashes.

 

Well if they revoked the boot loader, you won't get it to boot unless you either:

1- Get an valid/signed copy of an eventual new boot loader which is compatible with the current fuse configuration.

2- Modify and re-sign the current boot loader to skip the revocation fuse checking.

The boot loader is signed/hashed with a 2048 bit key which is different from the one used for XEX files. This effectively makes the option 2 highly unlikely.

The public part of the bootloader key pair is present on the CPU MASK ROM and starts with "DD88AD0C".

This key seems to be the same for both retail and dev but of course it's private part of the pair is being kept at a secure vault somewhere at Microsoft HQ.

 

Nice understatement . Last time I checked (*), state of the art was to get 768 bit numbers (232 decimal places) factored, and it took years and many hundred machines to do so; or ~15000years on a single one. 1024 bit (which I would be interested in for some nondisclosed reason) is assumed to be thousand times harder, but may become possible within the next decade. For the time being, 2048 is completely out of reach (**).

Just my 2€c, in case anyone is considering trying to crack this. You'd considerably increase chances by getting a job at MS's 360 division :lol:.

(*) http://eprint.iacr.org/2010/006.pdf
(**) i.e., if the key was properly generated. Integer factorization is an odd problem, and becomes waaaaayyyyy easier if the number satifies certain properties. Small or known/tightly-bounded difference of the factors being the most prominent one :033:.

 

Well it was an offical 05 Xenon 'Reviewer Kit-1' as per what the motherboard version sticker says. I'd think those would be long retired/replaced by now, so I'm guessing these types were blacklisted unless anyone has anything to say against that.

-Doom