Test Kit to Development Kit

first 2 fuselines
0xc0ffffffffffffff
0x0f0f0f0f0f0ff00f

 

Test to Dev Shadowboot
Yes, it exists. Only two people have it.

 

Source? Knowing what goes into a test kit shadowboot, I have my doubts. In order to properly sign a test kit rom you need retail private keys, which would be way more valuable than any test to dev conversion. There's no point in sharing something like that without any content behind it; it's all rumors and heresay until I see some proof (files, code, technical documentation, demo)

 

My friend Brandon has an XNA Test kit that is running RGLoader online with NiNJA. He's a close friend of ED9@xbls.ninja/tyedye81 which is the guy who gave him the files. Brandon moved on from the xbox scene, you can try contacting Tye himself though.

I was also talking to my other friend Nigel once about RGLoader running on a test kit and he told me "it's a very different process on a test kit, it's not like a dev."

 

I can try to get a picture of his test kit running RGLoader though, he even told me how long his test kit takes to load the kernel due it booting into a normal test kernel, shadowbooting into dev, and shadowbooting into RGloader

 

I wasn't aware that tydye was with XBLS. Do you know if he had to flash his NAND (with a dev kernel) first? Or if he removes the shadowboot it is just a plain test kit?

 

They don't give info out but i was told this:
It needs test to dev shadowboot in order to be able to run RGLoader
Other notes:
Brandon sent tye a test kit so that RGLoader for test kits can be made.
A guy on instagram @micah_lawton has a test kit running RGLoader online, i never bothered asking how it works though.

 

Maybe you can flash a DEV filesystem to a TEST and you'll have full dev privledges?

 

The Test kit kernel (on the NAND) is what I would think would prevent anyone from making shadowboot ROMs. Where devkits check the ROM's signature against a devkit specific, *accessible* key, test kits use a retail key, which is closely guarded by Microsoft. The only thing I could think of to get by this would be replacing the test kernel on the NAND with a dev kernel, which would allow you to use the non-retail key; however, XDKs still protect their boot process like retails -- one way you can get around that is using an internal escalation function like HvxExpansions or HvxKeysExecute in a modified bootanim.xex . It's a long rabbit hole, but it comes down to needing private keys.

 

I would'nt be surprised if Tye had those keys, he's a smart man. Knows his devkit **** really well.

 

There's definitely a method, maybe i can show something in a video some day..