Post by: Agent ME on November 08, 2005, 06:35:00 PM
I boot it up. MS Dashboard comes up. Appears through software as an unmodded xbox. Only 3 saves:
SID3 Mechassault: Run Linux
And 2 "Yourself!Fitness" saves. Did someone attempt to softmod this xbox?
I try and think of ways to tell if its modded - and I think to test a burned SlaYer's disc and several retail (from-store) games on it. I get dirty disc error on some, and the "May need DVD Playback kit to watch DVD Movies" even when its a game I'm putting in. Ok, so it's got a faulty DVD drive.
So - how can I tell if this is a real dev system? Is there something on the inside other than a pin-header which could've been put in by someone who got it that would reveal if it is a dev kit? Any way to figure out what the debug IP is to contact if it is even running a debug BIOS?
I know another way to check - Try and access XBL, and it says it could connect to xbox live from the network settings menu, but I don't want to try it with an account and a game which may ruin my account (it would flag the account if I do get the Xbox Modified Console Error").
PS: Is this the right forum for this? lol.
PPS: I haven't yet opened this thing up myself.
Post by: Alex548 on November 08, 2005, 06:44:00 PM
The retail motherboards had a chip labeled MCPX and the dev kits had some other label (possibly MCP X or just MCP) Not exactly sure, but take a look at the Nvidia chip and let us know what it says.
Post by: Agent ME on November 08, 2005, 06:49:00 PM
If its not a debug but still has an LPC header, I think I'll throw on a cheap mod chip, load it with a debug BIOS, get a better DVD drive (or just borrow the samsung from my other xbox when I absolutely need one in) and make myself a new debug kit. Just no extra RAM for me unless I magically get ub3r-soldering skills.
Post by: Agent ME on November 08, 2005, 07:23:00 PM
I am NOT able to confirm the version of the xbox motherboard using the tutorial from the main page of xbox-scene. I am brought to here after following the tut. Conexant Video chip, No fan on GPU, 2 rows of pins on the power connecter. I'll check the serial number later - xbox is halfway apart with DVD drive still connected and about impossible to turn over in the current state. This appears to be a 1.2 or 1.3 by the tutorial.
Does anyone have some pictures of what the motherboard of a 1.2, 1.3, and 1.4 look like so I can compare to this xbox?
Also the hard drive is... different. Thin, with mainly white sticker saying it is a Seagate Model ST310014ACE. 16,383 CYL - 16 HDS - 63 Sect - LBA 20,005,650. Anyone know what that means?
I'm confirming there IS a pin header installed on the LPC. It is missing one of the pins though, the left, second one from front of xbox, pin. I remember on my 1.6 xbox I had to remove 2 pins on the pinheader before I installed my X3. I guess its something like that.
Now for the NVidia chip. It says exactly on it:
QUOTE
nVIDIA
MCPX X2
FA9025 . 1A 0240D1
S TAIWAN
MCPX X2
FA9025 . 1A 0240D1
S TAIWAN
Post by: fghjj on November 08, 2005, 08:20:00 PM
Post by: Agent ME on November 08, 2005, 09:14:00 PM
Post by: Pikkon on November 08, 2005, 10:14:00 PM
Like in this pic.
Retail xbox's have X3.
Does it boot up the XDK dashboard.But all in all you got a very good deal.
Post by: Agent ME on November 08, 2005, 10:39:00 PM
Okay, I'll tell you my results with the SlaYer's disc when I do that tommorrow or whenever.
Now if it reads the SlaYer's disc, that means its using the debug BIOS. So if that happens, I connect FTP to the xbox, check the files, and put the needed Xbox-side XDK on?
And if I use DVD2XBOX, will it show the 128 MB RAM at the bottom?
Also, the Hard drive is a 10gb. Is that normal for dev kits? I'd think they'd have like 20gb HD's.
Also, any other chips I should take a look at to help confirm this xbox as a dev kit?
Post by: haza55 on November 09, 2005, 03:24:00 AM
2. That is a v1.5 power supply i think
3. check under the motherboard for more ram chips
4. yes they come with an lpc preinstalled
5. they say development kit on the front or Debug Kit
6. The case is clear dark green for debug or clear for dev with a higher case
Post by: haza55 on November 09, 2005, 03:26:00 AM
Post by: Pikkon on November 09, 2005, 03:53:00 AM
same in alot of ways.Thats why your disc are not booting up.There are
tools available to do so.I would suggest finding infomation a dev and debug
kits before posting.Like on here.Try putting a audio cd in your drive and
it should work.But you said it boots the retail dashboard.It can only be
two things.One would be that someone used the recovery disc and
selected the retail dash,or you have a beta live debug kit.
Which is meant for live beta testing.And if you have one of thoses
you can do a whole lot with it at all except live beta test games.
But one way to find out is too get the recovery disc.If it boots up
than you have a debug kit.If not than you have a beta live debug kit.
Post by: Agent ME on November 09, 2005, 04:03:00 PM
And I was pretty sure a dev kit was a lot like a modded xbox just with a few more things like more RAM and the background debug TSR-like thing that lets things like Xbox Neighboorhood connect. Is there somewhere here I can read up a lot more things about it?
Also - would a dev kit boot a SlaYer's disc? I don't see why it wouldn't.
And what other differences are there between a Live beta kit and a real debug kit?
Post by: Agent ME on November 09, 2005, 04:42:00 PM
Post by: Agent ME on November 09, 2005, 04:59:00 PM
Can I use xISO and burn a disc with quake2x's default_devkit.xbe and see if it plays that?
Post by: Agent ME on November 09, 2005, 05:27:00 PM
Post by: Agent ME on November 09, 2005, 06:12:00 PM
So... is a debug kit's HD unlocked? I'm wondering if I can put it in my chipped xbox and FTP to it, like put on EvoX.
Or is it locked?
Post by: haza55 on November 09, 2005, 11:53:00 PM
and dev kit do read burnt dvds but make sure u have a debug xbe on that disc
Post by: haza55 on November 09, 2005, 11:55:00 PM
Post by: haza55 on November 09, 2005, 11:56:00 PM
Post by: bucko on November 10, 2005, 02:49:00 AM
http://www.hydras-wo...oxretailtodebug
Post by: Pikkon on November 10, 2005, 03:43:00 AM
QUOTE(bucko @ Nov 10 2005, 09:56 AM)
Ignore the bios bit on this, but this might be of help setting up XDK.
-
Title: Problem With Dev System
Post by: Agent ME on November 10, 2005, 08:33:00 PM
-
If you want photos look at the ebay link. Even an inside pic. Can't see specifics to clearly, like writing on a chip, but you can count whats there and tell there's an LPC pin-header.
So... is there like something in an xbe that's easily changeable that defines if it is runnable on retail/modded xboxs or devkit xboxs? And this program deXBE changes it so devkits can read it? And I saw a program "ParchHeader" that said it'd make devkit xbes to retail/modded xbes? Am I correct on my thinking?
Also, with Quake2x (port of quake2) (Available off xbins at XBOX > GAMES > Quake2xBeta3) there's two xbe's. default_devkit.xbe default_retail.xbe. My modded retail xbox (with X3 BIOS) will load either one. What's the difference? Is the default_devkit for use on dev kit xboxs?
I'll try the thing Pikkon just mentioned.
PS: It says my Avalaunch (Avalaunch v0.49.1 (build 62)) is already for debug. That normal?
-
Title: Problem With Dev System
Post by: Agent ME on November 10, 2005, 09:10:00 PM
-
Ok, this comp doesn't have a dvd burner (I only have cheap burnable CD's that are known for xbox's unability to read them, and burnable DVDs which I hope that work). Let me try burning this on other comp.
Otherwise I'll need to rush to store to reburnable CD...
So if I get Avalaunch running on dev kit, I can FTP over debug kit files right?
-
Title: Problem With Dev System
Post by: Agent ME on November 10, 2005, 09:46:00 PM
-
OMFG L33TZ0RS!
I burned the Avalaunch disc and put it in... its running!
I got FTP connection - full access to all drives. Resembles an unmodded xbox. Not even a E/devkit folder. Definetely a sort of retail restore done.
Just Avalaunch just being Avalaunch, it locks up every 30 seconds... Maybe I should try burning EvoX or UnleashX (with debug fix obviously).
-
Title: Problem With Dev System
Post by: Paintballpsyco2369 on November 11, 2005, 12:41:00 AM
-
A Development Xbox has a USB port on the back for a keyboard or mouse; it also has a Serial Port for Kernel debugging. Also on the Dev unit, there is a port similar to a Scusi port. It has a extra circuit board on the inside, slightly different cable (internally) 128 mg ram, and the software on the hard drive. A debug is basically a normal xbox, with a pin header already installed on the LPC bus, it has 128 mg ram as well, as a blanked EEPROM. Plus the Debug has a see through green case that says debug on the front, and the Den unit has a clear case with development kit on the front. Also on the Dev unit, the lid sits higher than on the on retail, or debug xboxs to accommodate the "extra stuff". Other than that the software that runs them if basically the same, just you can use more parts of it on the Development unit, such as the Kernel debugging, emulating, and the mouse and keyboard. The Development units are more for software developing, and the Debugs are more for testing, and other things. I hope this helps answer your question.
-
Title: Problem With Dev System
Post by: haza55 on November 11, 2005, 01:02:00 AM
-
If any of u have seen the halo 2 doco u see the devolpers and usally they have 3 to 4 xboxs each one devkit which are the more expensize kits and 2 or 3 debug consoles and they have usb keyboards that plug into the xbox usb ports at the front.
man just burn a recovory disc, place in ur xbox and on ur pc run the recovery wizard.
-
Title: Problem With Dev System
Post by: Pikkon on November 11, 2005, 03:53:00 AM
-
Post by: Agent ME on November 10, 2005, 08:33:00 PM
So... is there like something in an xbe that's easily changeable that defines if it is runnable on retail/modded xboxs or devkit xboxs? And this program deXBE changes it so devkits can read it? And I saw a program "ParchHeader" that said it'd make devkit xbes to retail/modded xbes? Am I correct on my thinking?
Also, with Quake2x (port of quake2) (Available off xbins at XBOX > GAMES > Quake2xBeta3) there's two xbe's. default_devkit.xbe default_retail.xbe. My modded retail xbox (with X3 BIOS) will load either one. What's the difference? Is the default_devkit for use on dev kit xboxs?
I'll try the thing Pikkon just mentioned.
PS: It says my Avalaunch (Avalaunch v0.49.1 (build 62)) is already for debug. That normal?
Post by: Agent ME on November 10, 2005, 09:10:00 PM
Otherwise I'll need to rush to store to reburnable CD...
So if I get Avalaunch running on dev kit, I can FTP over debug kit files right?
Post by: Agent ME on November 10, 2005, 09:46:00 PM
I burned the Avalaunch disc and put it in... its running!
I got FTP connection - full access to all drives. Resembles an unmodded xbox. Not even a E/devkit folder. Definetely a sort of retail restore done.
Just Avalaunch just being Avalaunch, it locks up every 30 seconds... Maybe I should try burning EvoX or UnleashX (with debug fix obviously).
Post by: Paintballpsyco2369 on November 11, 2005, 12:41:00 AM
Post by: haza55 on November 11, 2005, 01:02:00 AM
man just burn a recovory disc, place in ur xbox and on ur pc run the recovery wizard.
Post by: Pikkon on November 11, 2005, 03:53:00 AM
QUOTE(Paintballpsyco2369 @ Nov 11 2005, 07:48 AM)
A Development Xbox has a USB port on the back for a keyboard or mouse; it also has a Serial Port for Kernel debugging. Also on the Dev unit, there is a port similar to a Scusi port. It has a extra circuit board on the inside, slightly different cable (internally) 128 mg ram, and the software on the hard drive. A debug is basically a normal xbox, with a pin header already installed on the LPC bus, it has 128 mg ram as well, as a blanked EEPROM. Plus the Debug has a see through green case that says debug on the front, and the Den unit has a clear case with development kit on the front. Also on the Dev unit, the lid sits higher than on the on retail, or debug xboxs to accommodate the "extra stuff". Other than that the software that runs them if basically the same, just you can use more parts of it on the Development unit, such as the Kernel debugging, emulating, and the mouse and keyboard. The Development units are more for software developing, and the Debugs are more for testing, and other things. I hope this helps answer your question.
-
Title: Problem With Dev System
Post by: Agent ME on November 11, 2005, 12:24:00 PM
-
As far as I can tell, debug kits are just newer versions of the dev kits. They're about the same, just one has a BIOS flasher, and DVD emulator. Which don't have too much need for.
I would burn a Recovery disk... if I had an .iso.
Anyways, here's some more info after using Avalaunch -
Version is DVT4/5, RAM 64.00 MB?! (Hopefully an error, or something to do with running from disk, or that the extra devkit stuff isn't installed to initialize it, maybe the extra 64 is "hidden" from most apps and solely for the debug stuff, I don't know. Can someone with a debug kit use Avalaunch and tell me what theirs says?)
Also I FTP'ed UnleashX to apps folder, but if I launched it it would go to MS Dash and say dirty disk. I could have sworn I fixed it in deXBE for debug...
-
Title: Problem With Dev System
Post by: haza55 on November 11, 2005, 06:10:00 PM
-
how many ram chips u got check top and bottom of the motherboard + what is there serial numbers
-
Title: Problem With Dev System
Post by: haza55 on November 11, 2005, 06:12:00 PM
-
I would kill for a dev or a debug kit
or 2 version 1 or 1.1 xbox mb so i can rip the ram chips of one and put them on the other
i have 2 xboxs only if i could programme in c++ i can only program in c#
-
Title: Problem With Dev System
Post by: Agent ME on November 11, 2005, 08:44:00 PM
-
Post by: Agent ME on November 11, 2005, 12:24:00 PM
I would burn a Recovery disk... if I had an .iso.
Anyways, here's some more info after using Avalaunch -
Version is DVT4/5, RAM 64.00 MB?! (Hopefully an error, or something to do with running from disk, or that the extra devkit stuff isn't installed to initialize it, maybe the extra 64 is "hidden" from most apps and solely for the debug stuff, I don't know. Can someone with a debug kit use Avalaunch and tell me what theirs says?)
Also I FTP'ed UnleashX to apps folder, but if I launched it it would go to MS Dash and say dirty disk. I could have sworn I fixed it in deXBE for debug...
Post by: haza55 on November 11, 2005, 06:10:00 PM
Post by: haza55 on November 11, 2005, 06:12:00 PM
or 2 version 1 or 1.1 xbox mb so i can rip the ram chips of one and put them on the other
i have 2 xboxs only if i could programme in c++ i can only program in c#
Post by: Agent ME on November 11, 2005, 08:44:00 PM
QUOTE(haza55 @ Nov 11 2005, 06:17 PM)
how many ram chips u got check top and bottom of the motherboard + what is there serial numbers
-
Title: Problem With Dev System
Post by: Pikkon on November 11, 2005, 09:15:00 PM
-
Well it looks like you dont have a real debug kit at all.You got ripped off.
You can tell from my personal pic of a debug kit motherboard.
http://photobucket.c...t=debugmobo.jpg
And here is yours.
http://bandjwholesal.../debugboard.jpg
Your motherboard is a V12 or V13 at most.
Dev kit (DVT4) motherboards are V10.
Debug kit motherboards are v.11
-
Title: Problem With Dev System
Post by: Agent ME on November 11, 2005, 09:45:00 PM
-
Sure? I know with xboxs the early versions had the fan on the GPU and the newer ones don't... sure you don't have an older version (that has other things different too) and I have a newer?
And that doesn't explain the LPC header (which looks unlike) or its inability to play retail xbe's. Or the nVidia chip.
And what exactly is it in the pictures that you say proves it?
But then - what do your debug kits say when you go into Avalaunch, settings, main, and look at memory? Does it say 64.00 Mb or 128.00 Mb?
-
Title: Problem With Dev System
Post by: fghjj on November 12, 2005, 02:47:00 PM
-
Post by: Pikkon on November 11, 2005, 09:15:00 PM
You can tell from my personal pic of a debug kit motherboard.
http://photobucket.c...t=debugmobo.jpg
And here is yours.
http://bandjwholesal.../debugboard.jpg
Your motherboard is a V12 or V13 at most.
Dev kit (DVT4) motherboards are V10.
Debug kit motherboards are v.11
Post by: Agent ME on November 11, 2005, 09:45:00 PM
And that doesn't explain the LPC header (which looks unlike) or its inability to play retail xbe's. Or the nVidia chip.
And what exactly is it in the pictures that you say proves it?
But then - what do your debug kits say when you go into Avalaunch, settings, main, and look at memory? Does it say 64.00 Mb or 128.00 Mb?
Post by: fghjj on November 12, 2005, 02:47:00 PM
QUOTE(Pikkon @ Nov 12 2005, 05:22 AM)
And here is yours.
-
Title: Problem With Dev System
Post by: Agent ME on November 12, 2005, 03:14:00 PM
-
Nothing about this xbox makes sense. I'm not sure if its fake or real, heck, the only solution seems to be like how quantum computers work. They can have 1, 0, Both 1 and 0, or neither. This thing seems to be fake and real at the same time.
Serial number tells its a version 1.4 while tutorial about opening it up says the inside is a 1.2/1.3 supporting the theory its a retail in debug case.
Softmod installer supporting its a retail with flashed TSOP.
I FTP'ed over an xbdm.dll, dashboard.xbx (pointing to \Device\Harddisk0\Partition2;xboxdash.xbe), and a devkit folder with xbdm.dll (look down for content) to E drive using Avalaunch, but could not connect to xbox after rebooting with Xbox Neighboorhood.
Avalaunch reporting 64.00 mb, supporting idea its fake (could be error)
Cannot play retail games or retail flagged apps, supporting the idea its using a real devkit BIOS.
Pin-header installed on LPC supporting its a real dev kit.
Abaility to use debug marked apps, such as Avalaunch off my disk and just recently ConfigMagic 1.6 from apps folder (launched from Avalaunch).
Also, this has to mean something - config magic told me the xbox has a corrupt eeprom and config magic forced me back to dash without letting me see anything useful (ERROR 4 Config Magic says).
And I still don't have a recovery disk...
-
Title: Problem With Dev System
Post by: Agent ME on November 12, 2005, 03:17:00 PM
-
And deXBE says that the Avalaunch I used DOES NOT have the limit 64 RAM flag on, but it has the "Don't set up Hard disk flag"...
-
Title: Problem With Dev System
Post by: Agent ME on November 12, 2005, 03:35:00 PM
-
WTF? deXBE when I patch something to debug, save it, quit, and re-open it, its still set to retail. And EvolutionX won't open in it.
I'd be able to fix this xbox so freaking fast if I had a recovery disk...
-
Title: Problem With Dev System
Post by: haza55 on November 12, 2005, 03:56:00 PM
-
Ok tell me
1. what mcpx or waterver it is is it a x3 or x2
2. what video encoder chip do u have
3. are there usb daughter boards
4. dose the pin header look like it was soldered on by a machine or a person
5 dose the ram chips look like they have been soldered on
-
Title: Problem With Dev System
Post by: Agent ME on November 12, 2005, 04:11:00 PM
-
Post by: Agent ME on November 12, 2005, 03:14:00 PM
Serial number tells its a version 1.4 while tutorial about opening it up says the inside is a 1.2/1.3 supporting the theory its a retail in debug case.
Softmod installer supporting its a retail with flashed TSOP.
I FTP'ed over an xbdm.dll, dashboard.xbx (pointing to \Device\Harddisk0\Partition2;xboxdash.xbe), and a devkit folder with xbdm.dll (look down for content) to E drive using Avalaunch, but could not connect to xbox after rebooting with Xbox Neighboorhood.
Avalaunch reporting 64.00 mb, supporting idea its fake (could be error)
Cannot play retail games or retail flagged apps, supporting the idea its using a real devkit BIOS.
Pin-header installed on LPC supporting its a real dev kit.
Abaility to use debug marked apps, such as Avalaunch off my disk and just recently ConfigMagic 1.6 from apps folder (launched from Avalaunch).
Also, this has to mean something - config magic told me the xbox has a corrupt eeprom and config magic forced me back to dash without letting me see anything useful (ERROR 4 Config Magic says).
And I still don't have a recovery disk...
Post by: Agent ME on November 12, 2005, 03:17:00 PM
Post by: Agent ME on November 12, 2005, 03:35:00 PM
I'd be able to fix this xbox so freaking fast if I had a recovery disk...
Post by: haza55 on November 12, 2005, 03:56:00 PM
1. what mcpx or waterver it is is it a x3 or x2
2. what video encoder chip do u have
3. are there usb daughter boards
4. dose the pin header look like it was soldered on by a machine or a person
5 dose the ram chips look like they have been soldered on
Post by: Agent ME on November 12, 2005, 04:11:00 PM
QUOTE(Agent ME @ Nov 8 2005, 07:30 PM)
I've opened it up. Things look a bit different than I'm used to - but I'm used to opening my 1.6 xbox, and the seller said this was 1.4.
-
Title: Problem With Dev System
Post by: Agent ME on November 12, 2005, 04:13:00 PM
-
Also, I have to decide by 3:00 PM (Pacific Time / GMT - 7) if I want to keep this thing or ship it back to the seller for a refund of my $160. About 40 minutes. Should I keep it? I think I should.
If all turns to worst, I can always end up putting it on ebay "POSSIBLE XBOX DEBUG/DEVELOPMENT SYSTEM" and start the bidding at $200, because even if its fake, its almost the equivalent of a modded xbox with a extremely rare case.
-
Title: Problem With Dev System
Post by: haza55 on November 12, 2005, 06:38:00 PM
-
ok u do have a real xbox debug
and the xbox ver is 1.2 or 1.3
-
Title: Problem With Dev System
Post by: Agent ME on November 12, 2005, 06:50:00 PM
-
The LPC pin-header is put in there very well, as good as the other things sticking out of the bottom.
I also took a lot of pictures, I'll host them in a zip somewhere in a few minutes.
-
Title: Problem With Dev System
Post by: haza55 on November 12, 2005, 06:56:00 PM
-
ok
now have u downloaded the xdk
-
Title: Problem With Dev System
Post by: haza55 on November 12, 2005, 06:57:00 PM
-
pm me ur msn so we can talk easyer
-
Title: Problem With Dev System
Post by: Agent ME on November 12, 2005, 07:00:00 PM
-
Add me
MSN+Email: [email protected]
AIM: AgentME37
-
Title: Problem With Dev System
Post by: Agent ME on November 13, 2005, 02:25:00 AM
-
I figured out why the debug kit only reported 64.00 mb of ram and did not use the xbdm.dll or anything -
a friend with XDK had a readme file on the recovery disk, and it said that the Retail Restore puts on MS Dash, allows xbox only to play debug beta games, limits 64.00 mb of ram, and will not connect to computer in any way (like Xbox Neighboorhood).
-
Title: Problem With Dev System
Post by: Agent ME on November 23, 2005, 06:26:00 PM
-
These screenshots should explain themselves and my progress:
-
Title: Problem With Dev System
Post by: Agent ME on November 23, 2005, 07:02:00 PM
-
So anyone know how to run retail games on this thing? (Without hardware hacks preferably)
And why aren't the pics showing?
Anyways, I ran the recovery disk, restored it to dev kit, now Avalaunch says 128.00 MB of RAM, and development kit kernel detected.
-
Title: Problem With Dev System
Post by: Agent ME on November 25, 2005, 05:21:00 AM
-
Come on, someone's gotta know a way.
-
Title: Problem With Dev System
Post by: Agent ME on November 25, 2005, 08:30:00 PM
-
Yeah I noticed some tut for games on debug by putting the game like its saved to the hard drive into the Game Development Volume (The XDK E: drive I think). Will that work?
And can this thing use Live? To what point? Can I point my account on this thing, go to MS Dash, see my friends online, message them and do features MS Dash lets?
What about in games? Could I save a game to the hard drive and play that on Live?
-
Title: Problem With Dev System
Post by: ole_dev_hacker on November 27, 2005, 10:03:00 AM
-
Dude you got a real dev / debug box you just really need the XDK Recovery Disc.... When I first got my dev box, It was in retail state. So I popped in the XDK Recovery Disc and restored it to Dev State, then applied hack_dev_kit to make it run whatever .xbe I want
Tho now I'm looking for a way to get a BIOS Loader to run on it so I can run the Dashboards that don't work well under a dev bios or a hacked dev bios 
Added ya to my MSN for in case you needed something just feel free to pm me or whatever 
ole_dev_hacker
-
Title: Problem With Dev System
Post by: haza55 on November 27, 2005, 01:35:00 PM
-
lol havnt been here for ages
ok
first off get the latest hacked debug bios
flash it with evox i think
then put evox in the application launch folder i dun wat it is cause i havnt used debug for about a month now
then launch evox with a configeration file that u made to point to the right dir s
and boot a game like h2 and tell me the results
-
Title: Problem With Dev System
Post by: Agent ME on November 27, 2005, 04:35:00 PM
-
Whats the name of the hacked debug BIOS? I can run it from BFM right?
Where is the hacked debug BIOS and a good BFM loader located on the usual places?
PS: I've already restored it with a 5849 recovery disk. I'm going to use the external recovery app to restore it to 5933 soon.
-
Title: Problem With Dev System
Post by: haza55 on November 27, 2005, 11:20:00 PM
-
umm try one of the complex bios
-
Title: Problem With Dev System
Post by: Agent ME on November 30, 2005, 09:28:00 PM
-
What exactly do I download? It looks like most of those BIOS are for retail-converted-to-debug xboxs.
-
Title: Problem With Dev System
Post by: Agent ME on December 02, 2005, 08:21:00 PM
-
What the heck??!?
This is kinda strange...
I tried putting on PacManX and Super Mario War, PacManX got an error when trying to load (XDK Launcher reported it - just like if you try and play Halo), so I deleted it, then I played Super Mario War, omg fun...
And I go to MS Dash to see if it makes a cool icon and save.
It didn't, but, I found 2 soundtracks that were never there before! I doubt Super Mario War put them on (I deleted them, tried Super Mario War again, they didn't come back). Anyways, the soundtracks were "Fighting Theme" or "Fighting" and then "Racing Music" or "Racing Theme". Two songs I remember on there were Journey and Ham.
Anyone know where these came from? This debug kit has been recovered to 5933 recently so don't say the previous owner put them on...
-
Title: Problem With Dev System
Post by: ShadowElitePro on December 02, 2005, 08:25:00 PM
-
Looks like you got a deal. Only 160.
-
Title: Problem With Dev System
Post by: Agent ME on December 04, 2005, 12:44:00 AM
-
Someone's gotta know how to get retail on this thing....
-
Title: Problem With Dev System
Post by: Agent ME on December 04, 2005, 12:44:00 PM
-
Where is it located on the usual places?
-
Title: Problem With Dev System
Post by: Agent ME on December 04, 2005, 02:21:00 PM
-
Got that, about to try and install.
Is this reversible, or if I mess up or put wrong file somewhere else fixable? I'm continuing now, I'll post what happens.
Can some tell me exactly what I need to do? THe translation of the file is horrible. When it says put in E:, does it mean the REAL E:, or XDK's E (Game Development Volume)? I'll try XE: first then real E: and see what happens.
Yes it works! I'm using my map pack disk (Retail) to install new Halo2 maps, and Halo2 works!
-
Title: Problem With Dev System
Post by: Agent ME on December 04, 2005, 03:38:00 PM
-
Ok, would it be safe to use UnleashX to format F:, and then use that other tool I saw somewhere to give F support to XDK launcher?
-
Title: Problem With Dev System
Post by: Agent ME on December 07, 2005, 09:12:00 PM
-
Ok, that's fine, because this is just the 10gb stock hd.
-
Title: Problem With Dev System
Post by: Agent ME on December 08, 2005, 08:21:00 AM
-
Its on Ebay now!
BST Topic Link
Ebay Link
-
Title: Problem With Dev System
Post by: old engineer on December 08, 2005, 12:01:00 PM
-
....So all that fecking around, creating one of the longest threads on xbox-scene, and now your bored with it and selling it on ebay, lol, classic
Post by: Agent ME on November 12, 2005, 04:13:00 PM
If all turns to worst, I can always end up putting it on ebay "POSSIBLE XBOX DEBUG/DEVELOPMENT SYSTEM" and start the bidding at $200, because even if its fake, its almost the equivalent of a modded xbox with a extremely rare case.
Post by: haza55 on November 12, 2005, 06:38:00 PM
and the xbox ver is 1.2 or 1.3
Post by: Agent ME on November 12, 2005, 06:50:00 PM
QUOTE
SAMSUNG 337
K402632380-QC50
K402632380-QC50
The LPC pin-header is put in there very well, as good as the other things sticking out of the bottom.
I also took a lot of pictures, I'll host them in a zip somewhere in a few minutes.
Post by: haza55 on November 12, 2005, 06:56:00 PM
now have u downloaded the xdk
Post by: haza55 on November 12, 2005, 06:57:00 PM
Post by: Agent ME on November 12, 2005, 07:00:00 PM
MSN+Email: [email protected]
AIM: AgentME37
Post by: Agent ME on November 13, 2005, 02:25:00 AM
a friend with XDK had a readme file on the recovery disk, and it said that the Retail Restore puts on MS Dash, allows xbox only to play debug beta games, limits 64.00 mb of ram, and will not connect to computer in any way (like Xbox Neighboorhood).
Post by: Agent ME on November 23, 2005, 06:26:00 PM
Post by: Agent ME on November 23, 2005, 07:02:00 PM
And why aren't the pics showing?
Anyways, I ran the recovery disk, restored it to dev kit, now Avalaunch says 128.00 MB of RAM, and development kit kernel detected.
Post by: Agent ME on November 25, 2005, 05:21:00 AM
Post by: Agent ME on November 25, 2005, 08:30:00 PM
And can this thing use Live? To what point? Can I point my account on this thing, go to MS Dash, see my friends online, message them and do features MS Dash lets?
What about in games? Could I save a game to the hard drive and play that on Live?
Post by: ole_dev_hacker on November 27, 2005, 10:03:00 AM
Tho now I'm looking for a way to get a BIOS Loader to run on it so I can run the Dashboards that don't work well under a dev bios or a hacked dev bios Added ya to my MSN for in case you needed something just feel free to pm me or whatever ole_dev_hacker
Post by: haza55 on November 27, 2005, 01:35:00 PM
ok
first off get the latest hacked debug bios
flash it with evox i think
then put evox in the application launch folder i dun wat it is cause i havnt used debug for about a month now
then launch evox with a configeration file that u made to point to the right dir s
and boot a game like h2 and tell me the results
Post by: Agent ME on November 27, 2005, 04:35:00 PM
Where is the hacked debug BIOS and a good BFM loader located on the usual places?
PS: I've already restored it with a 5849 recovery disk. I'm going to use the external recovery app to restore it to 5933 soon.
Post by: haza55 on November 27, 2005, 11:20:00 PM
Post by: Agent ME on November 30, 2005, 09:28:00 PM
Post by: Agent ME on December 02, 2005, 08:21:00 PM
This is kinda strange...
I tried putting on PacManX and Super Mario War, PacManX got an error when trying to load (XDK Launcher reported it - just like if you try and play Halo), so I deleted it, then I played Super Mario War, omg fun...
And I go to MS Dash to see if it makes a cool icon and save.
It didn't, but, I found 2 soundtracks that were never there before! I doubt Super Mario War put them on (I deleted them, tried Super Mario War again, they didn't come back). Anyways, the soundtracks were "Fighting Theme" or "Fighting" and then "Racing Music" or "Racing Theme". Two songs I remember on there were Journey and Ham.
Anyone know where these came from? This debug kit has been recovered to 5933 recently so don't say the previous owner put them on...
Post by: ShadowElitePro on December 02, 2005, 08:25:00 PM
Post by: Agent ME on December 04, 2005, 12:44:00 AM
Post by: Agent ME on December 04, 2005, 12:44:00 PM
Post by: Agent ME on December 04, 2005, 02:21:00 PM
Is this reversible, or if I mess up or put wrong file somewhere else fixable? I'm continuing now, I'll post what happens.
Can some tell me exactly what I need to do? THe translation of the file is horrible. When it says put in E:, does it mean the REAL E:, or XDK's E (Game Development Volume)? I'll try XE: first then real E: and see what happens.
Yes it works! I'm using my map pack disk (Retail) to install new Halo2 maps, and Halo2 works!
Post by: Agent ME on December 04, 2005, 03:38:00 PM
Post by: Agent ME on December 07, 2005, 09:12:00 PM
Post by: Agent ME on December 08, 2005, 08:21:00 AM
BST Topic Link
Ebay Link
Post by: old engineer on December 08, 2005, 12:01:00 PM