Print

[digisatman]

QUOTE (Angerwound @ May 19 2004, 07:55 PM)

Seems as though the latest update was aimed at us doubledash users. Therefore, a word of precaution to those currently using this exploit, don't run Live or you will be surprised with an ERROR 21 upon reboot. I guess the next update they won't be able to tell us about will have to do with the Easter Egg.

dont ya feel special angerwound, rmenhal and devz3ro?              

[PedrosPad]

[devz3ro]

NOTE: minimum donation for $50usd  

-devz3ro

http://sh0x.tk/

[Angerwound]

HAHA, maybe someone from MS will send you some dough for helping them discover a hole in the programming since they obviously read these forums. I'm sure they got all kinds of it lieing around. "Look Bill, there's that million bucks that fell out of your wallet the other day, let's donate it to devz3ro!"

[devz3ro]

.

Hopefully it's from M$ so I can sue and get more than $50

If not, I hope it was worth it.

Just thought I would share this  

-devz3ro

http://sh0x.tk/

[jon20usa]

 that is unless it was m$.

[Xboxhakur_band]

Glad to see someone finaly used the easter-egg idea.
Now if someone would examine dashupdate.xbe, I still believe that would be the key to beating the time-stamp checks. (older dashupdate.xbe's use the fonts from the root of C:)

[rmenhal]

QUOTE (Gage @ May 20 2004, 11:07 PM)

That stability issue that people have that is mentioned at the beginning of this thread, is that when the xbox live button is selected and the exploit freezes after seeing the dashboard wiremesh. It worked for a while and i only started seeing this problem today. Would the fix be that whole enlarging the landing zone thing.

Are you already using the fonts with 15 MB ernie? If not, try them. Even if they're still causing problems, there's something to be done.

Also note that launching the (15 MB) exploit with an audio CD will freeze it hovering inside the green wired sphere. Something to do with deleting all those .xip files with "music" in the name.

[wivenhoe123]

ADVICE NEEDED! thanks.
well i already got a modded xbox, but the chip is old and starting to play up so i'm thinking of using the double dash exploit so can take the chip out. I have an xbox v1.0 with a 80gb hard-drive added into it running the latest Evox bios and dash.
I just need clarification on a couple of points of how to use the double-dash mod as i dont wanna mess it up (i seen too many error 21 screens before!!).
so if anyone can answer these that would be great.

as well as the double-dash package, what other files do i require?
To install it, what else do i need to do apart from copy the /C and /E folder from the package to the relevant drives?

Thanks
Mark

[jon20usa]

[devz3ro]

QUOTE (rmenhal @ May 21 2004, 05:17 AM)

QUOTE Now if someone would examine dashupdate.xbe, I still believe that would be the key to beating the time-stamp checks. (older dashupdate.xbe's use the fonts from the root of C:) A pretty good idea - the title ID in dashupdate.xbes is indeed different from 0xfffe0000. Unfortunately, they're not flagged HD-runnable, only DVD. Atleast that's the case with dashupdate.xbes I've got. That pretty much kills it. Allowed media can be checked using: xbedump dashupdate.xbe -dc. If there's no XBE_MEDIA_HDD in the output, then it won't do.

I believe a "XBE_MEDIA_HDD" flagged dashupdate.xbe does exist.

If you ever noticed, if you:

1: upgrade your dashboard to the latest "Live" enabled dashboard

2: delete all the contents of your C drive

3: downgrade to lets say 4920

4: upgrade to the latest "Live" dashboard again

It does not "re-download" any of the new dashboard files, it starts the update from the hard disk itself (I left the network cable in only long enough for it to find out it needed a update, then unplugged). Hopefully the dashupdate.xbe (if that is what is used) might be stored in the fatx or some other drive I am unaware of.

I hope this has been helpful, I might be completely off  

-devz3ro

http://sh0x.tk/

[Angerwound]

Very Interesting.

[PedrosPad]

QUOTE (Xboxhakur_band @ May 21 2004, 02:54 AM)

Now if someone would examine dashupdate.xbe, I still believe that would be the key to beating the time-stamp checks. (older dashupdate.xbe's use the fonts from the root of C:)

Not my area, but...

Surely it can only be the Pre-Live Dashboard to Live 1.0 Dashboard 4290 that could possibly have used fonts on C:\ - because after Dashboard 4290 installed, the fonts on C:\ were removed.  This was the, media bound, dashupdate.xbe that shipped in the retail XBOX!Live start up kits, and the initial XBOX!Live games (Splinter Cell, etc.).

Future Dashboard upgrades, downloaded from XBOX!Live, may well be cached on the HDD, but they won't be expecting to find any fonts on C:\, as, in order to reach the XBOX!Live console to initiate the Dashboard update download, you must already be running Dashboard 4290 or later.

[devz3ro]

Too bad the Xbox's launch dashboard was not live enabled or 4920 still relied on fonts in the root of C. We would be in the money then  .

But the reason for my post was to try and locate where dashupdate.xbe is & related files (regardless whether old or new) to see what other "neat" things we can find (maybe xbox live gamer tags & hopefully something useful to the exploit community)

-devz3ro

http://sh0x.tk/

[PedrosPad]

xbedump update.xbe -dc

CODE

XBE Dumper 0.5-BETA Release Certificate ~~~~~~~~~~~ Size of certificate                 : 0x000001EC Certificate timestamp               : 0x3E306D50 Thu Jan 23 22:31:44 2003 Title ID                            : 0xFFFE0000 Title name                          : "Online Updater Application" Alternate title ID's                :    none Allowed media types                 : 0x00000001                                    : XBE_MEDIA_HDD Allowed game regions                : 0x7FFFFFFF                                    : XBE_REGION_US_CANADA                                    : XBE_REGION_JAPAN                                    : XBE_REGION_ELSEWHERE Allowed game rating                 : 0xFFFFFFFF Disk number                         : 0x00000000 Version                             : 0x1012A700