Debug Bios On Xecuter2 Console
Posted 13 February 2012 - 05:46 PM
My problem is as follows: I want to be able to take clean, uncompressed game screenshots directly from the Xbox, and the only way to do it is via the debug bios, or a debug console (with a debug bios, obviously).
The Xbox I own is huge and black and it displays "xecuter 2" under the Xbox logo when it starts, and that's ALL I know. I have some sort of a menu in it that lets me boot emulators and such. I am also able to browse the HD via FTP.
I'd like to know exactly what is needed to accomplish what I'm after, preferably without screwing up my console as it is the only one I have. A step by step, idiot-proof guide would be nice.
Please, help a girl out.
Posted 13 February 2012 - 08:45 PM
You might consider a capture device that can connect to component.. it will be decent.
Posted 13 February 2012 - 09:05 PM
The menu once the Xbox starts is Evolution X. I have some programs installed already. One of them is called Xbox Bios Checker 4.0b by CrackJack. It gives me the following:
Chip Type -> MODCHIP (or unknown HomeBrew)
Using genuine BIOS -> Xecuter2 4983.67
Then there's the BIOS MD5 hash, which is too long to type, and irrelevant.
The Evolution X "Settings / Info" panel gives me this:
Kernel version: 1.00.4983.67
As I have mentioned, I can access the hard drive via FTP. I read about Phoenix Bios Loader. Is it possible to simply load the debug bios from a file?
Posted 13 February 2012 - 11:19 PM
I'd like to hear from someone who has done this before and might know which steps I should follow to achieve what I'm after on my setup. All I can offer for your help is being ETERNALLY GRATEFUL!
Posted 14 February 2012 - 02:08 AM
Posted 14 February 2012 - 08:10 AM
Posted 14 February 2012 - 08:24 AM
Unless your bios has been set to skip booting from the DVD drive, (highly unlikely) it will always boot any valid application from the disk first, regardless of the hard drive, and allow FTP access. Just make sure you never flash your bios.
Posted 14 February 2012 - 06:29 PM
- XDK Debug Dashboard 4627 or higher
- Bert and Ernie .xtf files
- Debug RC4 Key
- A 1MB Bootable-From-Media (BFM) version of the Complex 4627 Debug Bios (5558 BFM, and others work too)
- A backup copy of your original xboxdash.xbe file
I'm guessing the backup is, well, a backup, so I can make my own via FTP. The rest is a bit problematic to find and I have NO IDEA what the RC4 key is. Is it a file? A string of numbers? Do you extract it yourself? Does it change from BIOS to BIOS?
I know this isn't exactly "legal", but we're talking last generation here, so maybe you could at least point me to where I can get all that? Debug dash, dert & ernie, RC4 key and a BFM Complex Debug Bios? This stuff is hard to track down. PM me maybe?
Posted 14 February 2012 - 06:36 PM
Posted 16 February 2012 - 05:43 PM
It's either "LOL what's thaaat? LOLOL" or "I don't know" or I get the link to the only tutorial out there, and it's not really helping. Where am I supposed to go so that I can get some guidance? Everyone seems to be experts on flashing, backing up, burning and what have you, but the whole debug issue is a big mystery.
By the way, I did at least burn the Evox CD and it does boot, from the MS Dash as well.
Oh, while writing this, I finally found the RC4 key. That stuff is REALLY well hidden. Let's see if it helps. If not, I'll be back to whine and moan some more. In the meantime, if someone who knows how to do this correctly reads this, I'd appreciate ANY help.
Posted 16 February 2012 - 06:04 PM
Edited by Movax, 16 February 2012 - 06:06 PM.
Posted 16 February 2012 - 07:59 PM
I got the Phoenix Bios Loader to NOT FREEZE at the phoenix logo. I found a package containing a signed bios with the RC4 key. I simply extracted it to programs on one of the partitions and booted it up. The program starts and goes back to the Evox dash.
I thought that maybe this did the trick. That once this is done, the debug functions are active in the background. They're not. Not as far as I can tell.
This is unrelated, but ConfigMagic 1.6 Final gives me "Error 4 - EEPROM Corrupt!". What gives? How do we fix this? And should we?
Posted 17 February 2012 - 03:08 AM
There aren't many people involved with xbox1 anymore, and most that are (like me) have never setup a debug system, or if they have they have just flashed a debug bios, rather than using software. I will someday, but I haven't yet, so you are somewhat on your own.
AID Manual Appendix F.
Posted 17 February 2012 - 03:59 AM
I'm sure you'd be able to help with this thread more than I could...
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users