Beta 2 Prototype XeDK

My Beta 2 XeDK, which I have not turned on in ages and know nothing about, is a curious animal.

It has a 10552.0 flash and a 10552.0 XDK.

I can find information about JTAGs and RGHs all day long, but dev kits are a little more obscure.

My questions:
1) If I try to connect this thing to PNet, update it, or what have you, will it be banned instantly? Why? Is there a way I can deceive the XBL challenge system by making the hypervisor seem like a regular dev? (If this last question violates the "no hacking PNet" rule, please ignore it.)
2) Is there any way I can get retail games to play on here? I have a JTAG, but it is RROD and I am too cheap to repair it ATM. Generally speaking: is there any way I can get a bootloader (like Xell) to run the retail dash on here? Or are there too many restrictions within the Xbox's infrastructure to make this happen? If not possible, please explain?
3) What can I do with this console? So far I have only been able to watch movies and run FSD or XeXMenu. I can develop myself, but I am not overly enthusiastic about learning to code Win32 C++. I can and have made XNA games in C#; is this possible to do on my DevKit? What about if I update it?
4) I remember once on my JTAG using Xell I was able to boot a PPC architecture Gentoo Beta Live CD. Have any of you freed your DevKit from it's monolithic task of development and turned it into something cool? Like a computer, a dev, and a retail all in one?

tl:dr

Is this Beta 2 DevKit like regular DevKits? How can I update it safely? What can I do with it? How do you have fun with your dev kit?

I've been out of the loop for a while now, and am looking to beef up my man cave a little with the help of this old relic. Any advice would be appreciated.

Thanks a ton,
Decryptic

 

To my knowledge, these beta kits are running different encryptions from within the CPU, now that doesn't mean i CAN'T be unlocked, but i'm guessing the most important step would be to unlock the xex2 restrictions, but since i have heard nothing on this... and since information is so scarce on devkits (Especially Xedk's)

Resources and blogs i have read over the years about these beta kits seem to point to the CPU as the main problem, but also could just simply be a encoded difference in the nand compared to retail to disable it, picture it like having windows 8 beta, where as you can only run development programs and such things alike, but games or programs running regular .exe's would fail on load, at that point a simple BIOS alteration would unlock it, but since the NAND of the xbox360 isnt exactly the most *Readable* thing. and unless you have good knowledge about the files held in the nand, we would have to wait till someone cracks it.... that is if its even possible

Probably not the most helpful information here, but i'm in the same boat as you bud

 

Beta 2 or 009 kits as there sometimes known were generally repurposed to final kits. You should be fine running any recovery on it. The fact is your running an old but not the oldest recovery, this also suggests you have a re purposed XDK.

I had one myself and gave it away to be honest, had it for years and never had any troubles with it but knew a buddy who needed a kit so off it went.

Theres an app called 360 gamehack that will patch retail xex files to work on rev, but you will need to find a newer recovery. Try Googeling "XDKRecoveryXenon" you can check out my sales thread for recovery version numbers, just remove the .3 as I don't think that's public yet.

As for partnered, its whitelisted, you can't connect unless your IP is authorised to do so by your GDN account.
Hope this helps!

 

The age old question of how can I make an XDK play retail games....

Basically this, you can easily use the modified compatibility files to play Xbox1 discs. As for 360, without totally modifying the kit, cannot be easily done. If you're hell bent on playing retail discs on the kit; just rip the games with your jtag with the XeDK HDD attached, use X360Gamehack to change the Xex and DLLs to devkit, play builds off HDD or move builds to PC and burn to blank DVD-R.

But going in and hacking the hypervisor to play retail disc is borderline sacrilegious, just buy a retail for it and sell the XeDK.

 

Thank you for the helpful responses. X360Gamehack is a tool that I was unaware of, and is definitely what I was looking for.

@XboxSurgeon: oddly enough, things like FSD and XeXMenu work on both my JTAG and Beta 2, so, I think, assuming X360Gamehack acts similarly, I might be able to do this all on the dev.

Thanks again.

 

X360gamehack is a PC based application. Fsd and xemenu are dev kit signed to work on jtagged consoles and xdks. X360gamehack will allow you to resign the builds so they will play on an xdk. Most home brew is built with the official SDK which is why they will work on all the consoles mentioned.

 

Thanks, that explains a lot. I always thought Devs run any and all unsigned code, never knew there was a dev signature too.

Status update:
On my computer, I had an extracted copy of Portal 2 ripped right off of my JTAG. This one worked on the JTAG, so I'm not worried about the copy.
I had X360Gamehack mull through the folder and do its thing. It patched and backed up the originals alongside in a bunch of .orig files.

My patches:
All region
All media
Make devkit
Minimum lib version
Remove revocation check
Remove keyvault restrictions
Remove encryption
Remove bounding path
Remove bounding device id
Remove console id restriction
Remove date restriction
Remove system updates

I unchecked all of the Xbox1 patches.

Upon running the new xex the first time, my console shut off, and then booted into what looked like a kernel dump, presumably because something went wrong. In Hdd1:\DEVKIT\dumps\launcher_360.dll there is a file called xboxkrnl.exe.dmp. I am pretty sure that was not there before. After reopening XeXMenu and running the xex again, it took me back to the dev dash without saying anything and continues to do so. This is unlike what it was doing with the retail xex, stating simply that it could not run the game.

X360Gamehack did something. I'm hoping that one of the patches I selected only works with exploited retails. Any patches there that seem suspicious; that I should obviously remove? Like the media or region patches?

I am determined to get this to work. Why, I am unsure. I could just buy a JTAG. But I want to see this thing run games.

Let me know. Any and all advice is appreciated.

 

What did the dump say? Can you post it here. Also, you can leave xbox 360 gamehack's default settings on, even the xbox 1 stuff. Just make sure that its set to make devkit on the 360 side

 

Is your dashboard new enough to run the game your trying to run. Removing library version checks are ok provided the library hasnt changed dramatically.
Typically you would get a dirty disc error when running a incorrectly signed xex file, the fact your getting a crash dump makes me wonder if its lib related.

 

Make yours look like mine, scan the ENTIRE build because DLLs and XEX(s) are all scanned with this program, delete the xex.default.org because there isn't a need for it afterward, put newly scanned build back on your kit, start default.xex (or feel free to change name to whatever if on HDD, has to be kept default.xex if you build it on a disc), game starts = PROFIT

 

XboxSurgeon: I have all of those checks selected save the xbox one patches, so I doubt that will do the trick. But thank you, now I know all of these checks should work for my dev. I do also scan the entire build. Something like 30 dlls are modified.

wan5: This is a good suggestion. I knew that the dash must play a bigger role in the game's execution than I thought. This console is on 10552.0, which I suppose should be new enough to run Portal 2. But possibly not. Any links on how to update 360 dev firmware? Should I just connect it to the internet?

kebob:
Let's see...
Wow it's 82 MB...
Ah Visual Studio knows what to do with it...

 

Ive sent you a pm, give that a shot and let us know how you get on.

 

I can't be the only one here who is jealous this guy has a beta 2 xedk tho right?

 

Nope! I am jelly over it. I can always use another

 

For those helping DeCrYpTiC to get Portal 2 running on xdk I can say it does not work on 21256.3. I have had this issue since I have had the game. Not sure if its the version or what but it never ran no matter what dash I was on. It loads the initial Valve logo but then before it gets to the start screen it freezes(for me cause I have dump disabled).

 

Hmm. I have portal 2 on my corona with sidecar running 21256.3 with no issue... That's odd you're having issues with it. I'm not home but I will check my build when I do eventually get home and I will PM you Drachir regarding it.

 

It could very well just be the version I have for some reason or another does not like me... ;(

 

You say that like they are handed out like bags of chips xD, though i'm quite sure if you wanted to, with the selling/buying expertise you have, that wouldn't be too hard lol

 

Fantastic news, gentlemen, the damn thing runs games. Thanks to those of you who suggested X360Gamehack, and an enormous thanks to wan5 for the update suggestion.

The thread lives, though.

A minor question:
Does anyone know how to return to the dev dash while in the regular dash for a 2xxxx flash? There is no (DEBUG) option like there was before, and I've been forced to reboot the console numerous times to get there.

 

Return to Launcher or using neighborhood to launch the xshell.xex from flash. However it sounds like you need it more to be on the console then needing a computer so I will send Return to Launcher your way