Leaked Microsoft internal document retail to dev

Well theres a document floating around, that some how says that by hardware modifications you can turn a retail into a dev. It states you can use a retail BOM (bill of materials) meaning you can some how buy everything you need to make this.

 

Y, it's floating. But not an internal document. And as i know, without to know how to programm the fuses useless.

 

^

 

It was sent to repair factorys for a specific error code. You can't do shit with this without the software and other documents that go with it.

 

Well is it possible to program the fuses from the xbox itself using the same hypercalls used to increment the LDV?

 

Great, just what we fuckig need.

 

You really can't do shit with this.

 

Hmm well, I actually have a theory

"Prior to making any of the following changes for any of the Xbox 360 Console platforms, the MTE Team requires that a new dev BOM for the console and PCBA be created (via ECO) by copying over the selected retail PCBA and Console BOMs (which will create new part numbers) and updating the programmed flash assembly and test suites within the BOMs."

Basically, think of this way, there is a hack to change a 512mb ram to a 16mb ram, and it only required to change a resistor if I remeber correctly.
Basically I think this is telling us, that by changing some values on some components on the motherboard, either adding them, or replacing them (such as transistors, resistors etc), it says the BOM's change (which right now im assuming is like bill of materials)

But then after you do all of this, you kinda loose yourself at this step

"5) When building into a console, stuff the following Lamprey cables following standard installation procedures:
X801796-001 CABLE ASSEMBLY, MOBO, LAMPREY, SMC KERNEL DEBUG PORT
X801797-001 CABLE ASSEMBLY, MOBO, LAMPREY, SPI PORT

6) Reset the console type from Retail to Dev (Agile doc H03710)
RETAIL 00000002
DEVELOPMENT 00000001
"
It makes no sense what so ever, how are we supposed to change these values, before they actually told you what to change as far as parts go, but here its like ehh...

Even after you do all this how are you supposed to build a nand image with cpu key that works?

 

Ahahahha, Just as xenon said. It's pretty much useless, unless you have the right stuff.

 

.

 

You could easily do this if you could make the right hypercalls.
setting r0 to 0x22 burns the efuses; all you have to do is reverse the hypercall and make it burn the right fuses instead of the LDV`s

How do you think M$ does it? Magic?

 

Wouldnt it be easier to emulate the dev fuses as the nand replacements do? Ive often wondered why this wasnt the method used to be honest, it would have stopped all that cod cheating none sense.

 

Well looks like this does detail atleast the hardware part, I indeed was some what right, I am checking a retail and dev mobo, and finding alot of the differences listed in this article

yeah checked everything, instead of stuff or non stuff the document actually means replace or remove. I compared 2 xenon mobos, and indeed the configurations were as described in difference between retail and dev.

The last part is where you just don't know what the fuck to do.

 

The last part will be using their software that is described in the docment number they have.
The software itself will be only on some of the top computers at the repair facility so I doubt you'll be getting your hands on them anytime soon.

 

No no no no no, no no, no no, no. There is more to HvxBlowFuses then just calling it. And it's a syscall, not a hyper call. The software is called the hypervisor, and it has syscalls or system calls.

The lock down values are only checked in the first bootloaders. When the rebooter kicks in we are allready in the kernel, almost at full boot.

 

You could make use of this if you were repairing dev units.

This would allow you to make the necessary changes to a retail board, that would allow the swap of cpu/nand from dev2retail.

For example, the partly trashed mainboard consumer waste boxes we have all been looking at.

 

Those partly trashed consumer waste devkits have already been fixed up. God bless the chineese.

 

Well lets just hope this gets interesting. Might be worth something in the end, you never know.

Hawk

 

LOL
Its nothing more than instructions on how to turn production retail HW into devkit HW, prior to fuse blowing/programming. There is no magic.

 

lamprey - anyone have got info about this board? for blowing eFuse?
phoyto/info etc?