xboxscene.org forums

Pages: 1 [2] 3 4

Author Topic: Xmtaxbox.xbe?  (Read 300 times)

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Xmtaxbox.xbe?
« Reply #15 on: June 18, 2004, 03:09:00 PM »
QUOTE
When the Xbox kernel initializes, it checksums the EEPROM. If it fails, the Xbox will be in DEBUG mode, i.e. the region code is set to 0x80000000.
<snip />
This XMTAXBOX.XBE is an XBE retail-signed for hard disk, also with the region code set to 0x80000000,

It may be we need to zap our EEPROMs to get this to launch - the exploit could restore it before launching a game, but then how do you zap it again in time for the next boot?

Just thoughts....
Logged

RiceCake

  • Archived User
  • Hero Member
  • *
  • Posts: 788
Xmtaxbox.xbe?
« Reply #16 on: June 18, 2004, 03:12:00 PM »
Well hell, if this works either way I'm happy. Worst thing about softmods is the fact that you can mess up your EEPROM - and the show's over...

As for zapping - unzapping, can't you just use a kernel-level EEPROM? That way the hardware can stay blank.
Logged

Chicken Scratch Boy

  • Archived User
  • Hero Member
  • *
  • Posts: 1054
Xmtaxbox.xbe?
« Reply #17 on: June 18, 2004, 03:57:00 PM »
i think the first thing to do is get a copy of this xbe and  get a guy with a chip to run it, see if we can see how it works

then we can start peeking into the hex and looking for vaunerabilities
Logged

Angerwound

  • Archived User
  • Hero Member
  • *
  • Posts: 928
Xmtaxbox.xbe?
« Reply #18 on: June 18, 2004, 07:36:00 PM »
Someone could purchase a brand new box and hot swap it the first power on..
Logged

afon

  • Archived User
  • Full Member
  • *
  • Posts: 160
Xmtaxbox.xbe?
« Reply #19 on: June 18, 2004, 07:37:00 PM »
Pedros-
Zapping and unzapping? Im unfamiliar with those words. If you referring to messing with an EEPROM on each boot, i think we should stay away from that (As it has a certain amount of times it can be written to). As long as the people with new xboxs can open thier drive on boot, then tap it in to play a backup...they should be fine.

But i have a question about the MCPX setting the ROE flag. When the xbox enters the error screen when ROE is enabled...it doesnt reset on eject. Is there anyway we could find what flag is being sent to MCPX and use it to our advantage?
Logged

Australian Rat

  • Archived User
  • Full Member
  • *
  • Posts: 139
Xmtaxbox.xbe?
« Reply #20 on: June 19, 2004, 12:04:00 AM »
QUOTE (Yod@ @ Jun 19 2004, 08:09 AM)
Post Removed...

I wouldn't say that here... even if people are looking for it.

Get it around the 'usual ways'.  Don't offer for PMs.  You'll regret it.
Logged

m.e

  • Archived User
  • Jr. Member
  • *
  • Posts: 95
Xmtaxbox.xbe?
« Reply #21 on: June 19, 2004, 02:29:00 AM »
QUOTE (Yod@ @ Jun 19 2004, 08:09 AM)
edit

Great! biggrin.gif
Logged

BluhDeBluh

  • Archived User
  • Full Member
  • *
  • Posts: 135
Xmtaxbox.xbe?
« Reply #22 on: June 19, 2004, 03:17:00 AM »
It looks like this might be a goer having just done a xbedump -da.

It works on all regions, it is signed for the HDD, and it hasn't got the CRC32s of the two .IN files internally so it means the exploit people can modify those files. Looking in it via hex, the file uses z:\BUFFER.IN and z:\FFT.IN.

Only one flaw with this is that every time you run a game, the Z drive is deleted, so you might have to reinstall the exploit every time...

Either way, it's VERY intresting. Cheers Yod@ smile.gif
Logged

Angerwound

  • Archived User
  • Hero Member
  • *
  • Posts: 928
Xmtaxbox.xbe?
« Reply #23 on: June 19, 2004, 03:32:00 AM »
Yod@, be careful you bound to get a ban or possibly a warning for offering of M$ copyrigth material through PM. But awesome on the finding either way.
Logged

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Xmtaxbox.xbe?
« Reply #24 on: June 19, 2004, 03:59:00 AM »
QUOTE (Yod@ @ Jun 19 2004, 08:09 AM)
I've got these files - XMTAXBOX.XBE off the X partition, and the BUFFER.IN and FFT.IN from the Z partition.

If anybody wants them, PM me with your email address.

Yod@, what XBOX version did you find these files on?
Logged

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Xmtaxbox.xbe?
« Reply #25 on: June 19, 2004, 04:09:00 AM »
QUOTE (Yod@ @ Jun 19 2004, 01:04 PM)
They're from a V1.5 Xbox. *I think*. It's brand new, anyway.

Ta. And what Kernel version does the Dashboard's 'system info' page report?
Logged

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Xmtaxbox.xbe?
« Reply #26 on: June 19, 2004, 04:24:00 AM »
QUOTE (Yod@ @ Jun 19 2004, 01:04 PM)
They're from a V1.5 Xbox. *I think*. It's brand new, anyway.
EDIT: Kernel version 5101.

Ta. muchly Yog@,  I'm off to play biggrin.gif

But if anyone happens to find copies of these on a new Kernel 5713 or later XBOX, I'd also be intrested wink.gif
Logged

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Xmtaxbox.xbe?
« Reply #27 on: June 19, 2004, 04:32:00 AM »
Yod@,
Without posting your XBOX serial number, please can you post your XBOX's manufacture date.  The following link shows your where to find it, serial number format

I suspect the date of the files on the Z: drive will 'match'/'be close to' your manufacture date.  Which would confirm that these files are, in fact, output files, and may not be exploitable sad.gif.

(In which case I'll focus on the network aspect, and get ethereal installed smile.gif)
Logged

mkjones

  • Archived User
  • Hero Member
  • *
  • Posts: 810
Xmtaxbox.xbe?
« Reply #28 on: June 19, 2004, 04:36:00 AM »
QUOTE (Yod@ @ Jun 19 2004, 12:54 PM)
Ok, thanks for the heads up. At least it's not built with an illegally-leaked version of the SDK.  tongue.gif

I'm sure enough people have it now anyway.

Yod@ man!

(see what I did there ^? thats wordplay for ya!)

Anyhow! smile.gif Another day, another chance of an exploit..
Logged

Yod@

  • Archived User
  • Newbie
  • *
  • Posts: 2
Xmtaxbox.xbe?
« Reply #29 on: June 19, 2004, 05:00:00 AM »
Manufacture date 2003-08-06
Serial 5xxxxxx 33205

So that makes it 2003, week 32, made in China, production line 5?
Logged
Pages: 1 [2] 3 4
« previous next »