xboxscene.org forums

Pages: 1 2 [3] 4

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

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Xmtaxbox.xbe?
« Reply #30 on: June 19, 2004, 05:17:00 AM »

QUOTE (Yod@ @ Jun 19 2004, 01:53 PM)
Manufacture date 2003-08-06
Serial 5xxxxxx 33205

So that makes it 2003, week 32, made in China, production line 5?

Hmmmm.
The XBE file on X: is dated 2003-11-15.
The data files on Z: are dated 2003-12-05.  Not now, and not then - Odd  blink.gif
Logged

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Xmtaxbox.xbe?
« Reply #31 on: June 19, 2004, 05:46:00 AM »

XMTAXBOX.XBE's allowed media types = 0x00000001, XBE_MEDIA_HDD - exactly the same as 4290's Update.xbe.  Which means this won't help with ROE issues for double-dash users. sad.gif  May still help with a UDE for Kernel 5713+ users smile.gif

From examining the XBE it appears like it also used some additional external support files, that I suspect it deleted as it exited  (and since deleting a HDD file simply modifies the directory entry, the files contents are likely to still exist on the virgin disk - FATX undelete anyone?).

We've seen
z:\BUFFER.IN - I suspect this is a test sound sample/DSP program.  
z:\FFT.IN - This is a ASCII text file, either specifying sound sample tests (and their expected results), or reporting the output of the sound sample tests  (I suspect the latter as it's human readable).

but not seen
z:\surface.bmp - source?
z:\copied_surface.bmp - destination?
z:\%s-%s.bmp - used for dumped graphic test screen grabs?
Y:\xboxdash.xbe - Hmmmmmm.
z:\%s - anyone guess
z:\rawimage - graphic image, disk image? - who knows.
c:\MemoryUnitStressTest%d.txt - seems clear.

I'm backing up me XBOX 120GB HDD, before I execute this puppy.
Logged

wrayal

  • Archived User
  • Newbie
  • *
  • Posts: 39
Xmtaxbox.xbe?
« Reply #32 on: June 19, 2004, 06:30:00 AM »

http://www.xbox-linux.org/docs/manufacturing.html

*Removing moron-post - url is where info on first page is from...*

Wrayal

This post has been edited by wrayal: Jun 19 2004, 01:31 PM
Logged

RiceCake

  • Archived User
  • Hero Member
  • *
  • Posts: 788
Xmtaxbox.xbe?
« Reply #33 on: June 19, 2004, 06:41:00 AM »

*If* its caching all these files its possible that:

XBox boots using special disk.
The XBE first checks for the cache files, just incase it already did the testing.
System checks are run, and caches of the results are saved.
The EEPROM is written to and the hard drive is locked, dashboard probably installed.
The XBox reboots and the XBE is reloaded.
The XBE searches for and loads the cached files to send them to the server.

If this is so, badda-bing, no real worries of frying your system. Main problem is these caches would get overwritten very easily.

This post has been edited by RiceCake: Jun 19 2004, 01:42 PM
Logged

UGLYMONKEY

  • Archived User
  • Newbie
  • *
  • Posts: 44
Xmtaxbox.xbe?
« Reply #34 on: June 19, 2004, 11:25:00 AM »

Has anyone actualy executed this  .xbe yet??? and with what results?
Logged

RiceCake

  • Archived User
  • Hero Member
  • *
  • Posts: 788
Xmtaxbox.xbe?
« Reply #35 on: June 19, 2004, 06:02:00 PM »

Gotta wait for someone who's crazy enough to risk frying their EEPROM and hard drive...
Logged

Chicken Scratch Boy

  • Archived User
  • Hero Member
  • *
  • Posts: 1054
Xmtaxbox.xbe?
« Reply #36 on: June 19, 2004, 07:30:00 PM »

all they need is a modchip with a bios with embedded eeprom, allowing restortion
Logged

RiceCake

  • Archived User
  • Hero Member
  • *
  • Posts: 788
Xmtaxbox.xbe?
« Reply #37 on: June 19, 2004, 09:54:00 PM »

Yeah true, but still need a crazy bastard who'll have to recover everything should this botch.
Logged

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Xmtaxbox.xbe?
« Reply #38 on: June 20, 2004, 02:37:00 AM »

QUOTE (RiceCake @ Jun 20 2004, 06:47 AM)
Yeah true, but still need a crazy bastard who'll have to recover everything should this botch.

Someone call?  biggrin.gif .  Just need to finish backing up to DVD+RW's first smile.gif

PS Dissassembled this XBE last night.  Many of those files I listed appear to be output files.  Unless I can find some input files, there may be no way to inject out own code sad.gif.  Still looking through.
Logged

rmenhal

  • Archived User
  • Full Member
  • *
  • Posts: 102
Xmtaxbox.xbe?
« Reply #39 on: June 20, 2004, 03:45:00 AM »

How would you guys run this binary at boot? The region doesn't match so you would need to zap the EEPROM. On the other hand, if the EEPROM checksum doesn't match, the kernel doesn't have much reason to trust any of the EEPROM contents, wouldn't build the HD key and HD password out of it and the HD wouldn't get unlocked. So C:\xboxdash.xbe wouldn't get executed. The only thing that would get executed is D:\default.xbe with region flag 0x80000000.

Wouldn't zapping the EEPROM just give you a paperweight until you get a modchip?
Logged

RiceCake

  • Archived User
  • Hero Member
  • *
  • Posts: 788
Xmtaxbox.xbe?
« Reply #40 on: June 20, 2004, 07:38:00 AM »

Now I'm really confused. Ah hell this seems like a bad idea anyhow, we already have the safer way of loading UDE.

I guess this is just a project!
Logged

wrayal

  • Archived User
  • Newbie
  • *
  • Posts: 39
Xmtaxbox.xbe?
« Reply #41 on: June 20, 2004, 08:09:00 AM »

"Unless I can find some input files, there may be no way to inject out own code"

As this gets code from the network ("* retrieve the EEPROM contents from a network server * retrieve the contents of the system and data partitions from a network server") , might it be possible to do a PSO-style hack as on the GC?
(In above my head here, but Im guessing that as nouser was ever really meant to use this file, would there be a greater chance of finding some sort of buffer overflow in it eg. in the downloaded eeprom contents?)

But as to changing the region or whatever, I dont have a clue sad.gif. Anyone? Although it may be a difficult hack to implement at first, it just seems to me that it would be worthwhile as it would be the first universal softmod as it seems to have been used on all the xboxes until now, albeit Im sure MS could implement some new protection feature

Wrayal
Logged

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Xmtaxbox.xbe?
« Reply #42 on: June 21, 2004, 02:40:00 AM »

QUOTE (RiceCake @ Jun 20 2004, 04:31 PM)
Now I'm really confused. Ah hell this seems like a bad idea anyhow, we already have the safer way of loading UDE.

I guess this is just a project!

Kernel 5317 owners can't use the existing 'update.xbe' based UDE (Becuase their Kernel prevents the execution of legacy Dashboard code).  I'm looking for a MS signed, HDD flagged XBE that they may be able to use.

I agree, this one doesn't sound ideal (and rest assured, the search does continue), but this is all that's come up so far.
Logged

PedrosPad

  • Archived User
  • Hero Member
  • *
  • Posts: 1277
Xmtaxbox.xbe?
« Reply #43 on: June 21, 2004, 02:42:00 AM »

QUOTE (wrayal @ Jun 20 2004, 05:09 PM)
"Unless I can find some input files, there may be no way to inject out own code"

As this gets code from the network ("* retrieve the EEPROM contents from a network server * retrieve the contents of the system and data partitions from a network server") , might it be possible to do a PSO-style hack as on the GC?
(In above my head here, but Im guessing that as nouser was ever really meant to use this file, would there be a greater chance of finding some sort of buffer overflow in it eg. in the downloaded eeprom contents?)

But as to changing the region or whatever, I dont have a clue sad.gif. Anyone? Although it may be a difficult hack to implement at first, it just seems to me that it would be worthwhile as it would be the first universal softmod as it seems to have been used on all the xboxes until now, albeit Im sure MS could implement some new protection feature

Wrayal

My thoughts exactly - and my current project biggrin.gif.
Logged

Angerwound

  • Archived User
  • Hero Member
  • *
  • Posts: 928
Xmtaxbox.xbe?
« Reply #44 on: June 21, 2004, 09:08:00 AM »

smile.gif
Logged
Pages: 1 2 [3] 4