we know where it is (in mem) when it is booted it's normal way (hulk xboxdash.xbe)
some good news
i have a working ST.DB for cold boot > uber4020 dash > st.db > habibi
(using a NDURE C:\ along side it)
that is based on the "doublestdb" by rmenhal
the one that uses "BUFF" instead of "RIFF" as HEAD0 (the one that cleans up the music dir)
so now we just need to find the offset of 5960 dash from <<EggsBox>>
i will try to do a xbe (settings_adoc.xip) that just writes this offset to a file
here it is incase some wants to work on this.
CODE
;;;
;;; Compile: nasm -o ST.DB stdb.asm
;;;
BITS 32
stdbmemofs equ 1498BCh ; < fixed by 4920 dash
D5960_offset equ 00000000h ; what is it ? <<<<<<
mem_offset equ 0D004B694h + D5960_offset ; adrress when launched from 4920 only
bin_start:
.HEAD0 dd 'BUFF'
.HEAD1 dd (mem_offset-1498C8h)/4
.HEAD2 dd .start-.HEAD0+stdbmemofs
;;;
;;; Summary:
;;; 1) Remove the subdirectory 1498c8 (HEAD2) that Dashboard created.
;;; 2) Rewrite ST.DB to disk (because Dashboard gobbles it.)
;;; 3) Change the MS public key in kernel to habibi-key.
;;; 4) Load and run a habibi-signed XBE.
;;;
.start:
call .base
.base: pop ebp
jmp short .continuecode
;----------------
.xbestring db 'default.xbe',0
.trnumstr db 'T:\music\1498c8',0
.trnum dw $-.trnumstr-1, $-.trnumstr-1
.ptrnumstr dd .trnumstr-.HEAD0+stdbmemofs
.tmusicstdb dw 14, 14
dd 17E10h; "T:\MUSIC\ST.DB"
.dispose db 1
;----------------
.continuecode:
; jmp short $ ; make it hang <<<<<<<<<<<<<<<<
dec dword [ebp+.HEAD1-.base]
dec dword [ebp+.HEAD2-.base]
push dword [ebp+.HEAD0-.base-4]
call dword [12034h]; NtClose
push byte 26
pop ecx
xor eax,eax
mov edi,stdbmemofs+416
rep stosd
inc eax
stosd
mov dword [edi-12],21371h
push eax
mov ebx,esp ; File handle
push eax
push eax
mov esi,esp ; IO status
lea eax,[ebp+.trnum-.base]
push byte 40h
push eax
push byte -3
mov edi,esp ; Object attributes
push byte 1
push byte 4
push esi
push edi
push dword 10000h
push ebx
call dword [12040h]; NtOpenFile
push byte 13 ; 13 = FileDispositionInformation
push byte 1
lea eax,[ebp+.dispose-.base]
push eax
push esi
push dword [ebx]
call dword [120A0h]; NtSetInformationFile
push dword [ebx]
call dword [12034h]; NtClose
lea eax,[ebp+.tmusicstdb-.base]
mov [edi+4],eax
push byte 22h
push byte 3
push esi
push edi
push dword 40100000h
push ebx
call dword [12040h]; NtOpenFile
mov eax,512+12
lea edx,[ebp+.HEAD0-.base]
call .write
push byte 101
pop ecx
mov eax,512-12
.wl: push ecx
mov edx,10D70h; zeroes at 0x10D70
call .write
mov eax,512
pop ecx
loop .wl
push dword [ebx]
mov esi,dword [12034h]; NtClose
call esi
; add esp,byte 12+8+4
.patchpublickey:
mov ebx,dword [121A8h]; XePublicKeyData
test ebx,ebx
jz short .badexport
cmp dword [ebx],31415352h
jne short .badexport
cmp dword [ebx+10h],10001h
je short .keyfound
.badexport:
and si,0F000h
.findkernel:
mov ax,[esi]
cmp ax,'ZM'
je short .check
cmp ax,'MZ'
je short .check
.retry: sub esi,1000h
jmp short .findkernel
.check:
mov eax,[esi+3Ch]
cmp eax,0FFFh
ja short .retry
cmp dword [esi+eax],'PE'
jne short .retry
mov ebx,esi
.searchkey:
inc ebx
cmp dword [ebx],31415352h
jne short .searchkey
cmp dword [ebx+10h],10001h
jne short .searchkey
.keyfound:
.searchkeyend:
inc ebx
cmp dword [ebx],0A44B1BBDh
jne short .searchkeyend
cli
mov ecx,cr0
push ecx
and ecx,0FFFEFFFFh
mov cr0,ecx
xor dword [ebx],2DD78BD6h
pop ecx
mov cr0,ecx
sti
.loadrunxbe:
push byte 0
push esp
push byte 0
push byte 2
push 127C8h ; "\Device\Harddisk0\partition1"
lea eax,[ebp+.xbestring-.base]
push eax
mov esi,555A9h
call esi
.inf: jmp short .inf
;------------------------
.write:
xor ecx,ecx
push ecx
push eax
push edx
push esi
push ecx
push ecx
push ecx
push dword [ebx]
call dword [120D8h]; NtWriteFile
ret
;
%if $-.HEAD0 > 416
%error 416 bytes maximum!
%endif
times 512-$+.HEAD0 db 0
dd 21371h, 0, 1 ; An empty no-name track (for HD to HD copy)
times 52224-$+bin_start.HEAD0 db 0
QUOTE(xman954 @ Oct 3 2005, 01:50 AM)
some good news
Alright, I've been out of the scene for a while but was going to try this on my ntsc 5838 box. I'm still pretty confused but this is what i've been able to put together (can't someone just put everything in one posts instead of making jump post to post, lol)
using kingroaches ndure 2.1 i should have:
C\
Audio/
bios/
Fonts/
media/
shadowc/
xboxdashdata.17cdc100/ (with only? Default.xip, keyboard.xip, mainmenu5.xip, music_copy3.xip, music_playedit2.xip and music2.xip)
xboxdashdata.185ead00/ (with 4817 xboxdash.xbe renamed settings_adoc.xip)
xodash/ (with s1974272->s1994752 patched update.xbe)
msxboxdash.xbe
xboxdash.xbe
default.xip (from dash 4817)
mainmenu5.xip (from dash 4817)
bert.xtf and ernie.xtf (from here http://forums.xbox-s...post&p=1387970)
and
E\
Dash\
TDATA/fffe0000/music/ (with xman954s st.db)
{: dumdasme, that's similar to the setup I have on mine! :}
If you haven't yet, delete the 21 MB filler from shadowc (Ndure 2.1 preallocates that for easter-egging).
The 4817 stuff (incl. the bert and ernie in /C) wont work on a 5838, so delete those too.
The update.xbe in xodash should be the original one (the 185EAD00 version).
.
.
.
This test needs the Uber4920 xboxdash.xbe in C (the MS signed 17CDC100 version).
Also, copy /C/bios/bios.xbe to /E/default.xbe (as that's the habibi signed file this test's st.db launches).
If I haven't missed anything your Xbox should boot, look like "normal" (but only the Music tab will work) and the 10 button presses ("code" segment earlier in this thread) will hopefully trigger the audio exploit on your 5838...
need some help here
QUOTE
Cold boot->D:5960->"<<EggsBox>>"->ProbeEnabledUberDash
= REBOOT and no file write...(modchip ON, OFF = "not a xbox disk")
could someone test this out also...
what i did find is, if you run a probe xbe that has a kernal thunk
table in it, all the "normal X86" reg are the same value no matter how it
booted, DVD or eggsbox or evox, i must be missing something.
is it something to do with the CPU "protected mode" ?
i can add code to the probe to find what we need, but i just dont know what to do
then write it to a file (that part works good)
QUOTE(xman954 @ Oct 5 2005, 06:55 AM)
need some help here
Worked perfect on my ntsc 5838 using the generic fonts.
Sorry for the double post, but it wouldn't let me edit. I also tested this on an ntsc 4920 with generic fonts and it works. If anyone is interested in my final file setup look here
@dundasme
AFAIK, this bit is wrong:
msxboxdash.xbe (uber4920 [.17cdc100] one) needs to be the 185ead00 xboxdash.xbe
and
xboxdashdata.185ead00/
should note: 17cdc100 xboxdash.xbe as settings_adoc.xip
And i was wondering how i should save this PPF since i keep getting "this is not a valid ppf file" errors..
QUOTE(Cio @ Oct 6 2005, 07:48 AM)
@dundasme
QUOTE(PedrosPad @ Oct 5 2005, 04:08 AM)
Obviously try
Cold boot->D:5960->"<<EggsBox>>"->UberDash
works first! - in order to verify that all the UberDash support files are in place.
that was the first thing i did and that works fine
QUOTE
After injecting probe.bin into the UberDash, re-sign the ProbeEnabledUberDash with xbedump - as this recalcs the XBE section checksums! If you haven't already, it would be a good idea to rename the 'output file' from "bert.xtf", as we don't actually want this mistakenly read as a font at this point.
did that too, data.dat...
also with bert.xtf and ernie.xtf in the root of C:\ (even though there not used by NDURE)
i think the problem is:
the way it was intended to be booted was from the XBL tab of a newer
dash (not 5960) then you would do the audio hack using the doubleST.DB
that would, on it's first passCODE
;;; 1) Remove the subdirectory 1498c8 (HEAD2) that Dashboard created.
;;; 2) Read a replacement hack from the end of ST.DB and write it to the
;;; beginning.
;;; 3) Change the MS public key in kernel to habibi-key.
;;; 4) Return to Dashboard. <<<<<<<<<<
then the Return to Dashboard would then triger the probe in the 4920 dash...
but the (double)st.db still works coldboot>ProbeEnabledUberDash just no file write
as of yet, no file write...
can someone try to get it to write a file (any setup) ?
QUOTE
Sorry for the double post, but it wouldn't let me edit. I also tested this on an ntsc 4920 with generic fonts and it works. If anyone is interested in my final file setup look here
oops, I meant my ntsc 3944.
@cio- On the 5838 i can't use the settings_adoc.xip xbe because that has been fixed in this kernel. So instead, on both xboxes, i used the st.db to trigger the default.xbe in E\.
I'm not sure if how i have it setup i can access my live console or not, i don't use live so i can't really test it. Since I have the dualboot setup, can i access the live console or do i need to boot straight into the uber4920 dash's xboxdash.xbe?
QUOTE(dumdasme @ Oct 7 2005, 12:28 AM)
oops, I meant my ntsc 3944.
QUOTE(kingroach @ Oct 6 2005, 03:00 PM)
use a mime encoder..
QUOTE(Cio @ Oct 7 2005, 09:21 AM)
Could you elaborate just a little further...
I never did do 5 and 6, thx! (that explains alot)
disregard my last post, it seems i've gotten a little mixed up in a couple of areas. I misread something that said the st.db got fixed in the latest dashboards and somehow twisted that into my previous post.
so if i understand this right, this means how i have it setup is basically no different from the regular ndure setup. I was trying to figure out how my setup would give you live console access whereas the regular ndure setup wouldn't. So basically what I need is 5960 xboxdash.xbe-> <<Eggsbox>> -> uberdash4920 -> st.db.
So at this point, it is basically not possible to dualboot and mantain full live console access?
At least I can say that you can successfully use the st.db with the 5838 kernel which was the original reason for me posting.
dumdasme, thanks for confirming xman954's new version of the 4920 audio exploit works with the UberDash on a 5838! (Although expecting it would, technically, it's great to know for certain that it really does.)
If you have enough space left, you could add the 'settings3' and 'settings_panel' XIP's (just for shits'n'giggles) to enable its [Settings]->[System Info.] ... hardly anyone has ever seen it display K:5838 and D:4920 before.
STILL trying to find the offset but no luck so far,
did a stack dump (112 bytes) from coldboot and eggsbox boot
there are a few differences..
does any know of a app or xbe that will show FREE memory that will coldboot??
and anyone care to guess how large the offset would be ??
(ie: 10KB <offset < 50KB )
I'm totally confused now. I adjusted my setup, so now i load the 5960 dash, easter egg to load the 4920 dash, but then when i try to do the st.db, then it reboots the xbox back to the 5960 dash. But if I start out loading straight to the 4920 dash or do the ndure dualboot to the 4920 dash then I can do the st.db trick fine.
Any ideas of why this is happening?
in my 5101 xbox I am having another problem.. I modified the st.db slighly ( just edited the path /partition1\bios\).. first time I enter EEE, it returns me back to msdash.. then at msdash when I enter ee again, it just reboots the xbox..
Yippeee rmenhal!!!! Together with xman954 the possiblities are endless
WOW that was it !!!CODE
D5960_offset equ 00001B000h ; eggsBox
mem_offset equ 0D004B694h - D5960_offset ; adrress when launched from 5960>EggsBox>4920
and ST.DB (udstdb) works fine with 4034 too.....
for some reason i was stuck thinking the offset would be plus
but know it would be small
NP (eh..) will be happy too
Whoohah. Rmenhal in tha hizouse. Nice to see your name across the screen with again some outstanding info.
Nice work rmenhal! this fixed the problem I was having with my 5838.
QUOTE(rmenhal @ Oct 9 2005, 06:00 PM)
Decided to take a peek here after a long time.
.. so I assume it will work on all other kernels too.. it works in my 5101.. only MS can give us three exploitable .xbe in one dash..lol
QUOTE(xman954 @ Oct 9 2005, 11:51 AM)
NP (eh..) will be happy too


Ecstatic; the generic UDDAE st.db (with 00001B000h D5960_offset) works on my box, as does the kernel specific eh! 
GJ
Xbox: What happen?
HD: Somebody set up us the exploit.
Kernel: We get signal.
Xbox: What!
Kernel: Main screen turn on.
Xbox: It's you!!
xman954: How are you gentlemen!!
rmenhal: All your box are belong to us.
xman954: You are on the way to homebrew.
Xbox: What you say!!
rmenhal: You have no chance to check sig's make your time.
rmenhal & xman954: Ha Ha Ha Ha ....
P.S. nice to see you again eh 
(please excuse the rant, you all got me in a good mood on monday, not something that happens alot).
QUOTE(rmenhal @ Oct 10 2005, 06:27 PM)
That just stands for 'overwritten address', it's not any technical acronym. Those addresses
locate the pointer to a structure used by the XDK debugger (I think - I don't have the XDK.)
Ahh, of course! Now that makes sense. I wondered what all those fs:[20h]+250h and calls all over
the code were doing.
QUOTE(rmenhal @ Oct 10 2005, 06:27 PM)
Perhaps there is a writable function pointer in a fixed location somewhere in the
XBE (instead of the kernel), with a call close enough to the overwrite position, but I didn't
look for one. The exploit could be made kernel version independent with that.
Yes, that would be more elegant, but hardly necessary and may not even be possible.
Thanks for clearing that up! (It has been nagging at me for a while now.)
CODE
%elifdef MS_4627_01
OWA equ 80035C04h+250h; MS 4627.01
from the hulk st.db
ok, a few ?s about this ST.DB exploit.
1. I have problems getting the right 4920 uberdash. Slayers 2.5 comes with a 4920, but that's not the uberdash one. So, NP linked to a thread that has PPF files (I got them already) to convert the non uberdash from slayers 2.5 to the uberdash one. Do these patches create me a real working uberdash that I can actualy use?
2. The ST.DB that rmenhal posted, what habibi signed xbe does it load?
thanks in advance
Horscht
thanks to rmenhal it works fine, 3944.4034 so far..
http://forums.xbox-s...dpost&p=2973832
just put the offset in D5960_offset, 1B000h
and change the + to - in the next line, there is the 'generic'
both boot E:\default.xbe
slayers2.5 MSdash is all that you need + PPF patch
to get everything working
QUOTE(dus @ Oct 11 2005, 10:19 PM)
...I guess the kernel _specific_ ST.DB posted by rmenhal should work on a normal 4920 dash.
Checked it and it works fine. (On a 5101 box using PBL to load Evox M8 bios, don't ask...)
unfortunatelly, this can't be used without problems on krazie's Ndure installer. krazie's ndure doesn't come with smaller fillers, but a rather big shadowC.img. So krazie's ndure setup lacks the free space for this setup. Just thought I'd mention it.
Krayzie: maybe you should consider a slightly smaller shadowC.img on the next version of your installer and add a few smaller filler files. Just a suggestion, tho
I'm sure that when you are smart enough to figure this stuff out your also capable of playing with the shadow C a little like removing it and add a smaller one...
If this makes it to the next installer I ofcourse take care of all necesarry adjustments.
yeah, I just tried it (I didn't have any problems making myself a smaller shadowc.img, I was just mentioning it for the next version of your installer
), and it works fine. I had problems at first, because I forgot to habibi sign the UnleashX default.xbe
. I almost got pissed until I realized that. It works very good on my 5838 kernel. Thanks rmenhal and xman for your work.
What I'll do next, is to use the xbe shortcutmaker (there is one by the avalaunch team, I thnik), to create a shortcut xbe to the gamesave. I will put the shortcut (habibi signed this time
) into the root of E named default.xbe, and the gamesave should load.
all in all: thanks for all your work rmenhal and xman.
I haven't read this thread since the day it was made, and I don't have anything to offer, so I just read through it tonight for an update. I just wanted to say wow! It really says something when you can (re)introduce an idea and it can be made into a success in just a few days. It shows a lot about the knowledge, intelligence, and determination of the people of Xbox-Scene. (especially xman954 and rmenhal)
As I don't know much about this as you guys do, I think I have the following correct. The UDDAE exploit works like SCEEE does for UXE. Except this works with NDURE (which is even better). Basically, this can completely turn the sofmod on and off. I'm going to try and get this correct, but please correct me if I'm wrong and if I do get it wrong, sorry about trashing the thread and creating more confusion.
1. The normal, retail MS Dash (5960) would load.
2. Trigger the EEE by doing the <<Eggsbox>> thing.
3. This would launch the uberdash (4920)
4. You would load a retail CD and then go to copy, copy, a, a, a. ?? ( I have no idea)
5. This would launch a habibi xbe ??
How does Ndure work with this? Man, I must sound stupid, as I don't know much about the development side of anything.
Also, would this work like the SCEEE , where it would be turned on and off via a EEE Switcher? Or would it boot up to the normal 5960 everytime?
Congratulations on the great accomplishment you guys.
QUOTE(Textbook @ Oct 14 2005, 05:48 AM)
I haven't read this thread since the day it was made, and I don't have anything to offer, so I just read through it tonight for an update. I just wanted to say wow! It really says something when you can (re)introduce an idea and it can be made into a success in just a few days. It shows a lot about the knowledge, intelligence, and determination of the people of Xbox-Scene. (especially xman954 and rmenhal)
QUOTE(krayzie @ Oct 14 2005, 06:35 AM)
Also you don't need an audio cd to launch the audio exploit. (at least I asume this is the no cd version. I haven't tried it myself yet.)
it is the no CD version
and there is a blank sound track to copy (in the st.db itself)
no need for any thing else
also too the switcher xbe could rename
a real st.db to use in the modded state ( so you could have in game music)
then when switched off put back the hacked one
did anyone make a package for this yet?
... and if so can you please just give the correct name for it ... so I can go easter egg hunting in the usual places.
One of my xbox's still has uxe on it because I like the sceee exploit... it would be nice to have this type exploit on my ndure xbox's.
Thanks guys for figureing it all out!
{@ rgtaa: http://forums.xbox-s...dpost&p=3052414 @}
here is the new generic st.db xman emailed to me, includes any path support:
CODE
UEsDBBQAAAAIACKteTM5dBUJqAUAANsNAAAIAAAAc3RkYi5hc22VV3tP20gQ/9tIfIc5iYoiEs5O
XB7hrhKJE9G7UhAgtRKg09re4G1tb253XZJ++pvZTWI7adVrohjvPH4zO69dzs/PYXeHniNZzETO
gc9ZMcv5AEqmC+hKuLs/ioagTRofIYWESWV3x/OG7+7voN/DBX4/mOsZLycI4Xke/7eCoOeHfkaM
j0oY3uZEp5YzyqXmXk3uh5Z8x827cipVwYyQFnMtcUGQn/hNFeci+ZsvImbYWj+4INj3rCqTjBg3
7Llh0yfwq+Iiz2XCDB/J0ojnSlb6ihdSLVYY/ZEVu+FKC21+KEWWLll+y02lyns5Eap4YYrX1kiA
vhS5AnWn2rHCs9PhKAPPg+XnHP6Ajxd3MBVznkK8gPCs50PKNAJEb86O/X/kdKq5IVlC8PETDPGR
eYAw58Cfn/VQzjEraGcp7FnJCDc9PD4LM+hCC4qsslQprjW8ZLyE3AYN7U+VLJwHsswXbguX44vI
97w0hf0ouhjvO0pgKa9rm13a2+g0O/g9RK/+hD0YTcbj42g0gt8hREK/PxmeDU/6Tr9n9bVhynSt
hcM6VKj/19UN3F/DWyzAi9t7cqMu1ruqKJhaDOzKCw7gFrW+cjAZB13FqVA8MZgtcB7Ba2vvAPnM
QISRjSVTKSSKM8PTIwfTI5gXqtVlzRsJqdBf4HXME1Zp3tB8lnGccw3CHB047f4BjDJWPjsnrkSi
pJZTAzNbqfCFL0CU+EeVPCfkjMUiFl2kL82HB/BeshRYmYKqSmArES2eS0zMp+HYSYJLig0cRsBL
WJ57MdN8d4eeA28mZx6PZ8j6XMw8nUllIKE6LiueyJQ7faPKqtBGeWkM+/eDx6LSInl0Advv+EsB
zNEL7HVXwt2g01rt7sxqnBRW741MWlMWm2iEFoQd/KF3pBGcjAPfdgqGekbTgPwJiDCPOcFa/x4j
/lUk/PESg0858R9vcPeCxkNwnvIpq3JzhArWcYzU3f3t+/EHagJ01wERJH2bkRh4RPFSnqBjEvP6
gHE7tMXdpVg+fZ/ZWzNnlc42ub7ldsOnZW5WfDfuSG2lGC8Mh94xLSllyRzf5lJ5nM07nNEKq9rj
qejU8TwMA1JQHDNrpE7xXZSJZ8UdxamtrKJ2N+g9dXBknQRZbbuBH6M1PaNJQqMWMqzAnLclt5W0
WCm9u6YmNpW2Kjln1n8bDlsPLlitPdPBUEO2WN1+ve2Vhev4M/YzMGOUiCvD9UYIgzb4GlqL3R2w
74TWTldAY7T2Ip5vZKs+z542rfXRJ3ziQCN2ZOvWlmLj0GprbMZlWeutyBC34flWcc236mn7nCSw
nyvWhbidsbpV185RMqiMDsMnqsrN8u1lrXX/f0U/9AP/FxNAbpCbb4LeYdBb+Z2i3+3GW+/WjvLN
3PlB3W1t0C6BvuQDJ12zyUTgRyd+hln/xpXkGpgBf26JLWNtwJahXOLrS45vv5ofHLHMJJk7R/C4
GHgNMw8bV6E6/1MCzYWTJSc6iUJvm7vDPrcMfzKZjCf4yZbSKNmxIm4erV1l88MApzUOkyg6OR1G
x6hQ77Kt7OhTtwN3u5jHNHDr+fHQvqk9NRo/oNpozKcHlCe+4dpYgquXz+U374jm4pc6z6i+Ec8f
3/nWJuPmwLXG3NqBD7zNMmoY+3EF15fIbbPNIRdvzv06ZyGGoT3tcSVVs3g6bmyiS+dg9Yha96rr
E7Jj6adPK4oWrnPc6fidIb0+RusUO1fIio4358DG5rfvxgR/JMrpoHEtoTUB2b6wPTRwsbC7x1+r
YrfnZNoemW3Z7deft179zwqxFDerJnwlprDn7qnwFkLb3q+4UlLRAigGGgo2F0VV/IbivEyF3Zpn
RIEsmjB7h04/jcG3rDQFdy53wO9AQOfKRQm8mJkFlLJbsoKDUSzBO+gUDV1GYCQ9EzlbHDTBe71e
uAH/H1BLAQIUABQAAAAIACKteTM5dBUJqAUAANsNAAAIAAAAAAAAAAAAIAAAAAAAAABzdGRiLmFz
bVBLBQYAAAAAAQABADYAAADOBQAAAAA=
QUOTE(Horscht @ Oct 12 2005, 10:18 AM)

unfortunatelly, this can't be used without problems on krazie's Ndure installer. krazie's ndure doesn't come with smaller fillers, but a rather big shadowC.img. So krazie's ndure setup lacks the free space for this setup. Just thought I'd mention it.
Krayzie: maybe you should consider a slightly smaller shadowC.img on the next version of your installer and add a few smaller filler files. Just a suggestion, tho
{= Actually, UDDAE can be more easily implemented another (safe) way with krazie's Ndure 1.0. I wonder if any one reading this understands the MS dash's setup requirements sufficiently to realize how... =}
It's even easier for Ndure 2.1 users of course; they can now benefit automatically from its 21 MB "future use" filler...
Get kingroach's 3.0 (currently beta; see his sig) and do 'Add Ndure Toolset';
only have that option checked, it's in the UDDAE section, then:
copy the resultant E\ndts folder(&contents) on the PC over to the Xbox's /E/
(if you have existing MS dash soundtracks and want to keep them,
then rename your /E/TDATA/fffe000/music/ST.DB so it remains available)
launch /E/ndts/default.xbe (to start red LED, realC mode)
select 'Install Menu'>'Install UDDAE'
When you restart the Xbox it will behave as before, plus you can now get from the MS dash to the softmod by pressing:
[Music][blank soundtrack][Copy][Select][Copy][New Soundtrack]
<<Eggs|3ox>> (that's two '<' Symbols, Shift E, g, g, s, beta Accent '|3', o, x and two '>' Symbols)
[Done](uberdash starts)[Music][blank soundtrack][Copy][Copy][New Soundtrack][Done]
QUOTE(Ndure protagonist @ Dec 18 2005, 12:15 PM)

{= Actually, UDDAE can be more easily implemented another (safe) way with krazie's Ndure 1.0. I wonder if any one reading this understands the MS dash's setup requirements sufficiently to realize how... =}
{= The Audio folders/files can be replaced by others that consume their space... =}
For example, the previous post's steps could alternatively be performed (with no adverse consequences) after deleting these 21 MB consuming files from /C/Audio/AmbientAudio:CODE
AMB_05_ENGINEROOM_LR.wav
AMB_06_COMMUNICATION_LR.wav
AMB_12_HYDROTHUNDER_LR.wav
AMB_EC_Steam1.wav
AMB_EC_Steam2.wav
AMB_EC_Steam4.wav
AMB_EC_Steam5.wav
AMB_EC_Steam6.wav
AMB_EC_Steam7.wav
{&
Non kingroach Ndure users would need to launch a different XBE via the ST.DB though...
&}