That's one way to interpret it all but (believe it or not!) there's always been a real significance about it too eh.
SUDDENLY...
... M$ haven't yet released an updated kernel or dashboard, but they most likely will ... notice the thread's title, the post's edit and (most significantly) what it was indirectly referring to eh?

"UD-eh!" is what I personally refer to as the "Uber4920 Dashboard - exploiters' heaven!". I'm sure a few folks will "hate me" upon learning that I discovered it three calendar months ago, however, maybe they will become accepting of the "bigger picture" approach I've taken. Many, many more current and future members of the softmod community will benefit from it (re the M$ sentence above) when UD-eh! does get released ...
which will be at the discretion of (and by) the forum mods/leaders (not me, I'm just an 'exploit hunter') eh.

I've sometimes posted clues about it, such at the two "biggies" on the previous page, as I felt obligated to the community to share this in some way (and to provide the opportunity for others to "enjoy the thrill of the hunt" too). What it is ... well if you didn't clue in from "UD-eh!" (or "UDeh", originally) and haven't now that you've just read it's name, then think harder! Why I believe it's so significant ... it's literally the largest softmod discovery made so far,
potentially has at least three astounding capabilities, one of which could turn back time for some users and another that would force M$ to be even more on the defensive than they currently are eh!

____
Edit: added
potentially (re Pedro's following reply)...
eh. certainly has a cryptic turn of phrase.
I just wanted to say that he has proven to my satisfaction that he did discover the files that facilitated the UXE exploit ahead of my stumbling across them independently.
(So he's been looking into them longer, and may indeed have new information to share)
Given the nature of today (in North America at least), instead of more 'trick' wording here's a 'treat'... some straight-talk about the "Uber4920 Dashboard - exploiters' heaven!" a.k.a "UD-eh!" that might (just might) give M$ a 'fright'...
UD-eh! is M$'s secret dashboard; its version is 0x17CDC100 and it identifies itself as 4920. It's really significant because (unlike the widely known 4920's) it runs on all current Xboxes, V1.0-1.6, K3944-5838 with these features:Good idea. Their board spies would prolly PM too though eh...
*wants it*
are there, really, M$ board spies? hahaha

atomiX is teh winnar!!!11ONE; he correctly interpreted the clues and progressed it via related messages (which he's allowed me to quote the pertinent parts from) eh:
___
i'm guessing from the live servers...maybe downgrading the dash to a pre-live version and doing an update with a dashupdate of that particular version (4920 >august 15) but i don't think this dashupate would be freely available...

== You're guessing correctly, it's obtained from the live servers (but therefore a small part of the above is impossible) eh...
___
can you give me a hint? i'm kinda liking this little treasure hunt 
== (The "small part" re impossible was a factual hint eh...
)
RISK: it's currently unknown whether connecting to XBL to obtain it (or using its xboxdash.xbe) might result in a ban eh!
___
i'm tending to believe you need to log in with a MS dash version that is included with the XDK. i certainly won't try this though.
== Nope, it's obtained in a retail manner (but when M$ demands something outside the box, think twice about it) eh...
___
how about the disk cluded with a live starter kit
== If it was for Live 1.0 then that would be a way to overcome the impossible 'small part' of your "i'm guessing from the live servers..." message (the rest of which was correct). Doing that plus not doing everything M$ says when you're thinking "twice?" outside the box, is how it's obtained (assuming M$ still provide it, which I expect they do currently) eh.
___
is this when setting up an account or actually just when connecting?
== Just when connecting; having or setting up an account isn't required (but don't forget it's not without risk) eh. 
_______
Footnote: Coincidentally(?) I've been unable to connect to XBL since mid-October (and I don't subscribe to Live) eh...
You get out much eh?
I'm awaiting your next discovery 
thx eh.
can't wait to try it.
i'm still pondering if i should try it now and risk getting banned...
still got 6 months to go
so lemme get this straight. if you have a live v1.0 starter disk n u use that to update your dash you get the 17cdc100 dash or am i missing something. @ eh. if people do get this dash are you planning on telling anyone how to do the UD-eh yet or no.
hmmm... well...
The_Truth=majorly confused...
ok.. can someone please explain to me what the hell is going on?
QUOTE(mckenn88 @ Jan 2 2005, 12:56 AM)
so lemme get this straight. if you have a live v1.0 starter disk n u use that to update your dash you get the 17cdc100 dash or am i missing something. @ eh. if people do get this dash are you planning on telling anyone how to do the UD-eh yet or no.
nope, it's not available on starter disks. it's gotten from the live servers. i won't say anymore since i don't know if eh. wants me to discuss it...sorry
Potential usages of 17cdc100 are outlined in this linked post; I'm sure the detailed steps will be posted in the forum, at some point. Although it's "a nice to have", I personally don't think it justifies folks risking anything, unless they have a worthwhile usage for it (and in time the useful parts of it will no doubt get released) eh.
ok this is my last attempt to understand it. you downgrade to a pre-live dash, use a live 1.0 starter disc to connect to the live servers and upgrade and that gives you the 17cdc100. also how do you know if the starter disc is live 1.0. i have the one that has moto gp demo, mechhassault demo, and tetris full version. thanks
To determine whether a disc's dashupdate.xbe is Live 1.0, you can `xbedump` it and see whether its Version# starts with 10. However, it's not necessary to "downgrade to a pre-live dash, use a live 1.0 starter disc to connect to the live servers" (but that's one way to ensure you have the required setup to obtain 17cdc100) eh.
as soon as i can, (prolly this weekend)... i will dump my dashupdate.xbe from my live disk... and i will post my disk #'s to confirm the xbe without dumping it again...
Clarifications:
i) `xbedump {XBE filename} -dc` includes the Version#;
ii) the two retail releases of the Live 1.0 dashboard (10027100 and 1012A700) are also referred to as "version 4920";
iii) M$ ubers those 4920's via XBL, to 17CDC100, before updating them to the real Live version (for reason/s unknown) eh...
I dont thik u need live subscription.. first when I bought my xbox feb. 2004, it came with 4920 dash and then I connected it to internet and It downloaded 5659.03 dash and I dodnt have any live account..
maybe thats changed now..
any new news on this one yet???
@mckenn88: the "Uber Easter Egg Exploit" (UEEE) is still its most recent news eh.
@kingroach: you're right, a live subscription isn't required to obtain it eh...
@"(non)treasure hunters": go figure what i + ii + iii (practically) produces eh...
i = rename its xboxdashdata.1012a700 to xboxdashdata.17cdc100
ii = micro-dot it accordingly
iii = leverage an s1974272->s1994752
I'm thinking of breaking tradition and naming the potential "next evolution" as 'FUSE' (not 'UXE2')! Feel free to speculate eh.
QUOTE(eh. @ Apr 22 2005, 03:19 PM)
I'm thinking of breaking tradition and naming the potential "next evolution" as 'FUSE' (not 'UXE2')! Feel free to speculate eh. 
You dare to imply my UXE exploit needs improvement?
- lol
FULL UBER SCEE EXPLOIT?????...
F@#ked Up Sur EggsBox?
/me wonders the point of announcing this in such a way
Anyway, cool to hear - guess there must be something cool and new 
Let's hear it!
(OT: I'm also going to potentially "evolve" at this time. After this one, I'll no longer terminate sentences in my [previously annoying?] manner eh.
)
@Pedro: there have been many posters that I believe would have benefitted from its additional feature(s).
@wrayal: indeed ... kind of ... patience, 10...
do we even need an evolution?! i couldn't find any problems with the old one!
...perhaps you guys should take a vacation
can't wait to see what you guys roll out next
Edit: correction...QUOTE(eh. @ Apr 22 2005, 09:06 AM - part)
@Pedro: there have been
some posters that I believe would have benefitted from its additional feature(s).

@kingroach: I've calculated the above 'guesses' (as a percentage of the name I'm thinking of) and yours scored 39.13 more. 
___
9...
QUOTE(eh. @ Apr 23 2005, 06:54 PM)
@kingroach: I've calculated the above 'guesses' (as a percentage of the name I'm thinking of) and yours scored 39.13 more.

___
9...
Then its some kinds of SCEE variant indeed..
QUOTE
@Pedro: there have been some posters that I believe would have benefitted from its additional feature(s).
some people who wanna play XBL?..
hmm.. some kinds of xboxdashx.be.. that has bult in switch to go to modded state?..
at least tell us if the SCEE part was right...
i'm also guessing it's some sort of live compatibility upgrade?
hmmm.....
8...
----
FULL UBER SCEE EXPLOIT => x%
F@#ked Up Sur EggsBox => y%
x - y = 39.13
Live compatability?
"Additionally, UD-eh! provides a new opportunity that maybe, just maybe will 'spook' M$ a little... there's a way to boot the current M$ dashboard with UD-eh! embedded (which facilitates a Live compatible exploit, if the recent defensive measures haven't precluded that)!"
Perhaps?
Haven't been following closely recently (I kinda moved my time around a bit ;p), so maybe this has already been released or something...
Although not having all, 'FUSE' would have no less and maybe one or two more XBL compatibilities than UXE.
(BTW: the previous posts quoted opportunity would still be entirely XBL compatible, SFAIK, plus it doesn't suffer from ROE/J [whereas the MA and SC based alternatives do].)

(but it's all good fun, and he's normally does have something.
)
(@Pedro: this time the 'FUSE' is shorter.
)
___
7...
QUOTE(eh. @ Apr 25 2005, 06:57 PM)
(@Pedro: this time the 'FUSE' is shorter.

)
___
7...
lol
reminds me of a somewhat regrettable statement by one of my teachers ("You are screwing about so much - I have a VERY short fuse!!" - to roars of laughter ;p)
Enough with the cryptic posts already! 
*sits and wait patiently for 7 more posts*
If it has one or two more XBL features are you talking about access to the Live dash or game updates working without switching fonts?
My random guess: Full Updatable Softmod Exploit?
@azrm2k: your 'random guess' scores (x + 13.02).
@wrayal: I hope you're not offended (nor anyone else) but I suspect that my approach to this is unlikely to change.
___
6...
always being difficult eh. but i suppose it adds some flair to the XBE section, so why not?
most people seem to think the F is for Full. i'd go along with that, although i suppose it could have something to do with the Fonts too?
U i would assume would stand for Uber, as this is based on the uber dash and all uber dash derivatives tend to have the "uber" in their name. i do like the thought of U being Update though. the ability to update the dash in live would be pretty cool...though it would require the retail fonts being in the fonts folder....(are they?)
edit: perhaps also "Uberdash"?
S is where we seem to be confused. is it SCEE? or is it Softmod? as of yet, the SCEE exploit has really been the only way of gaining live dash access. S could stand for something else though i suppose.
E i would guess to stand for exploit...though i liked pedro's idea of eggsbox.
is the name somewhere in there? or are we missing words? i suppose we can wait a week to find out. (any significance to the day you're releasing it?)
This thread is getting hilarious ....
Go! Go! GO!
(ermmm this reply sounds kinda negative, didn't it? .... didn't mean it that way, curiously/patiently waiting for any development)
(Reply is just to show support for efforts, cheers guys!)
Fantasticly Uber Secret Exploit?
OR something like that?
Who knows.. all i know is i got myself a topic subscription.
Fonts/Final uber softmod exploit?
If that's not right at least tell me if i'm going on the right track at least.
According to the percentages you gave FUSE has 23 letters and x had 9 letters y didnt but mine (which i'll refer to as z) had 3 letters x didnt. Is that correct?
FUCK URSELF SCREWING Eh.'s (exploit)
so if x+13.02 = 60% i guess.. so I think we arent getting the FULL part right.. and its SCEE Eggbox.. so the exploit is F____ UBER SCEE Eggxbox
QUOTE(azrm2k @ Apr 26 2005, 05:36 PM)
Fonts/Final uber softmod exploit?
If that's not right at least tell me if i'm going on the right track at least.
According to the percentages you gave FUSE has 23 letters and x had 9 letters y didnt but mine (which i'll refer to as z) had 3 letters x didnt. Is that correct?
i like final....that's a good thought! (may or may not be right, but it's a good thought)
Final Uber SCEE Eggsbox?
perhaps eh. couldn't think of a name for it but wanted to call it "FUSE" so he's just tricking us into making the name
Since it's hard to supersede the UXE and any EEE based Exploit kinda sucks for it's fingerdancing I suspect something double dash based or similar....

+ correct supposition
+ correct assumption (I considered Uber4920 but decided against it)
+ it's one of those
+ correct guess
+ indeed there is!
___
@Soullar: it's had a number of comical moments for sure (and now it has a cheerleader). 
___
@Cio: you also scored more than Pedro. 
___
@kingroach: ahem (and this isn't "my exploit")! 
___
@kingroach & cmiz: only the "Uber" word matches the name I was thinking of. (=>
)
___
@cmiz: I've now decided what to name for it for sure (and it's different)!
___
@krayzie: I believe it has no less features than UXE, plus it definitely has an extra capability. 
___
@azrm2k: I applaud your (Mensan?) deduction skills, essentially solving my 'letters algebra' and the earlier riddle too! 
5...
----
So, 'FUSE' meant "Fonts Uber Softmod Exploit" and it might rival UXE ... how could that be possible?
Should we look for the extra "capability" on a removable media device?
(Like fonts that can boot the retail dash, but also boot an exploited dash from a cd/dvd)
the only "real" feature UXE is missing is xbox live capablity that's why I mentioned double dash or another way to trigger the exploit via the retail msdash. I hope it has live console acces otherwise it would have no real benefit over coldbooting.
QUOTE(eh. @ Apr 27 2005, 01:22 AM)
5...
----
So, 'FUSE' meant "Fonts Uber Softmod Exploit" and it might rival UXE ... how could that be possible?

Well Eh.. I've attempted to stay away from this thread as I was sure you'd drive me insane trying to figure out what you could possibly be up to. I've had some ideas tossed about in my head but if I know you..I'm way off.
Just wanted to ask if this allows unsigned code in a live compatible state or does it not cross these boundries?
"@wrayal: I hope you're not offended (nor anyone else) but I suspect that my approach to this is unlikely to change."
Nah, I'm not offended at all (in fact, frankly, looking back over my posts I find them a bit rude :\ ). It's a bit of fun! For me at least...
Wrayal
QUOTE(eh. @ Apr 27 2005, 02:20 AM)
@cmiz: "always being difficult eh.", hmmm, I much preferred Pedro's "eh eh? - You got'a love him."!

my comment was also meant in good nature, i find the guessing games to be entertaining.
well we've got the name now...but still not the exploit. is it a double dash derivative? perhaps launched through another executable? (not sure how it would be triggered though...perhaps the music menu seeing as nobody really uses that anymore anyways?) or perhaps the retail fonts have been edited...i guess we'll have to wait and see
wow, the tension, the suspense, I think I'm going into cardiac arrest...
If this is going to supercede UXE, then Live compatibility has to be one of the improvements, but I'll wait for the official word, only time will tell.
QUOTE(Angerwound @ Apr 27 2005, 03:58 AM)
Just wanted to ask if this allows unsigned code in a live compatible state or does it not cross these boundries?
If this were the case, would it not be allowed on X-S? I recall you saying that a current way to get backups on live! would not be revealed to the public?
QUOTE(anjilslaire @ Apr 27 2005, 06:58 PM)
If this were the case, would it not be allowed on X-S? I recall you saying that a current way to get backups on live! would not be revealed to the public?
there is ?.. I will pay $140 ( thats all I have) for that bios..
perhaps there is already a live compatible exploit out there, but I doubt we'll ever be graced with its existence, the old point of "too many cooks" (or too many people spoiling a good thing)
I always wondered what would happen if a portion of code were to be injected into the XBE of a game that would rewrite the BIOS in mem back to retail, and then continued executing, or a BIOS that could intercept the check implemented by XBL, but I'm unaware of the technical workings of the Xbox on such a level, so who knows what can be done.
QUOTE(Olipro @ Apr 27 2005, 12:17 PM)
perhaps there is already a live compatible exploit out there, but I doubt we'll ever be graced with its existence, the old point of "too many cooks" (or too many people spoiling a good thing)
Your absolutely correct on that one. Very few of the greatest exploits go public.
QUOTE
I always wondered what would happen if a portion of code were to be injected into the XBE of a game that would rewrite the BIOS in mem back to retail, and then continued executing,
Well, I wondered the same thing almost a year ago. In fact, I even got around to creating an application that was basically... like xbedump. The main difference being it would inject the patch back code on the fly into some padding within the XBE. Once there, the entry point of the xbe was pointed at this bit of code. That way when you executed the xbe it would return everything in memory to retail, and jump back to the original entry point of the game. This was never released because of obvious reasons.
Of course, I would never divulge this much information if the flaw unfortunately wasn't fixed.
You can thank MS's dash update right about the time of Halo 2 for that one.
QUOTE
or a BIOS that could intercept the check implemented by XBL
No Comment on that one..
It's always very interesting to see what pop's in the XBE exploits section.. "Good artist steal better ones copy" This isn't implying that the better artist stole an idea.. Better yet.. Improved an existing idea.. Keep up the good work eh! :-D
Uh oh, I'd better "nip this in the bud" - it doesn't cross over any XBL boundaries (SFAIA)!
I'm hoping it will be more the opposite and provide one or two XBL compatibilities that UXE might not have. I say "might" (again) because I don't have Live! and have limited knowledge of it - let's pursue that...
Do any of you know whether update.xbe's and downloader.xbe's work when the retail disc's coldbooted and UXE's installed?
Also, if either or both don't work with UXE, anyone know (for sure) what the cause of their issue/s is?
QUOTE(eh. @ Apr 27 2005, 03:20 PM)
Uh oh, I'd better "nip this in the bud" -
it doesn't cross over any XBL boundaries (SFAIA)!I'm hoping it will be more the opposite and provide one or two XBL compatibilities that UXE might not have. I say "might" (again) because I don't have Live! and have limited knowledge of it - let's pursue that...
Do any of you know whether update.xbe's and downloader.xbe's work when the retail disc's coldbooted and UXE's installed?
Also, if either or both don't work with UXE, anyone know (for sure) what the cause of their issue/s is?
On a cold boot with UXE installed. Your usual UXE install I might add. Update.xbe's will not function due to the fact they call the fonts. Downloader.xbe is fine as it makes no calls to the fonts at all and can be executed without a problem.
Since Uberdash 4920's ubdate.xbe has been used for UXE
and Uberdash 4920's xonlinedash.xbe has been used for UEEE (not sure about this?)
Does FUSE use the xboxdash.xbe and new wicked fonts that have no clock problems?
QUOTE(eh. @ Apr 27 2005, 04:20 PM)
Do any of you know whether update.xbe's and downloader.xbe's work when the retail disc's coldbooted and UXE's installed?
so it's going to be an updateable softmod? hmmm....very interesting (unless it's an update.xbe or downloader.xbe based exploit in which case even more interesting)
QUOTE(azrm2k @ Apr 27 2005, 08:19 PM)
Since Uberdash 4920's ubdate.xbe has been used for UXE
and Uberdash 4920's xonlinedash.xbe has been used for UEEE (not sure about this?)
Does FUSE use the xboxdash.xbe and new wicked fonts that have no clock problems?
it's actually the xbe files themselves that cause the exploit not to have a clock loop bug....not the fonts. not using xboxdash.xbe is what makes it forego the clock setting screen.
Regarding the previous page's posts:
@Cio: it's on the HDD...
@krayzie: per my next post...
@Angerwound: "usual UXE install" leads me to think you know at least part of what I'm up to...
@wrayal: n/p...
@cmiz: pleased to hear it, actually not and you probably have (if not, it's at "flying" and "sourcer" locations)...
@Olipro: per my next post...
QUOTE(eh. @ Apr 27 2005, 11:41 PM)
@Angerwound: "usual UXE install" leads me to think you know at least part of what I'm up to...
Well,the idea I have rolling around in my head must be correct then. I'm not around X-S much anymore, but if you'd like we can speak via email about a few things...
'[email protected]'.
(@azrm2k: you could have been, via its unusual places...)
Edit: "clarification"...
QUOTE(eh. @ Apr 27 2005, 10:41 PM - part)
@cmiz: pleased to hear it, actually
"we've" not
got that and you probably have
it already (if not, it's at "flying" and "sourcer" locations)...
___
4...
----
@Angerwound: thanks for your offer (that I'll bear in mind) and your .xbe feedback which, being so, indicates this would have an XBL compatibility that UXE doesn't! 
QUOTE
@cmiz: pleased to hear it, actually not and you probably have (if not, it's at "flying" and "sourcer" locations)...
download.xbe from Area 51 demo?..
i'm not seeing any other xbe files in the area 51 demo so i'm guessing that's not it.
...flying and sourcer? i've got no idea.
3...
----
Apologies dudes; that led you astray instead of helping you find it! ("fly'r" and "source'r" would have been better and "flying" and "sourcing" more accurate). Related details are not permitted, but hopefully this is: one's from a Legend and another's a Messiah's.
Hmm, something present might be the future - how could that be? Follow this http://forums.xbox-scene.com/index.php?act=ST&f=45&t=263586&view=findpost&p=1977935 link to the past and see if you can tell me!
hmmm....the "uber" xboxdash.xbe and the normal xboxdash.xbe would pull their data from different xboxdashdata folders right? perhaps that's something...
flying and sourcing?i'm still confused...
my guess is you mean krayzie the "x-s legend" and somebody else with 3000+ posts (i only see triggernum in this thread). krayzie mentioned doubledash...perhaps the uber dash is loaded first and an exploit can be run through it....but the normal dash's xboxdash.xbe can be run somehow?
just a general question, how does MS know if you don't have an up to date dashboard? i'm assuming they don't scan your C drive to check the xboxdashdata.xxxx folder (else a lot of people would be in trouble) and if they did, coldbooting wouldn't work. they know when to update though, is it the size of the xboxdash file? just curious...
QUOTE(eh. @ Apr 29 2005, 06:47 AM)
Related details are not permitted, but hopefully this is: one's from a Legend and another's a Messiah's.
Hmm, something present might be the future - how could that be? Follow this http://forums.xbox-scene.com/index.php?act=ST&f=45&t=263586&view=findpost&p=1977935 link to the past and see if you can tell me!

Crumbs! I'm beginning to suspect eh is the author of XBOX360 http://www.ourcolony.net/ cryptic site.
QUOTE(cmiz @ Apr 29 2005, 07:36 AM)
perhaps the uber dash is loaded first and an exploit can be run through it....but the normal dash's xboxdash.xbe can be run somehow?
just a general question, how does MS know if you don't have an up to date dashboard? i'm assuming they don't scan your C drive to check the xboxdashdata.xxxx folder (else a lot of people would be in trouble) and if they did, coldbooting wouldn't work. they know when to update though, is it the size of the xboxdash file? just curious...
M$ don't need to scan your C drive, they simply pick a few details out of C:\xboxdash.xbe - it's version, date, certificate, etc. and compare then against the 'latest' Dash available on the XBL server.
If c:\xboxdash.xbe is an outdated retail MS Dash, it'll be updated.
Also, from D:5960 (the latest M$ Dash), the c:\xboxdash.xbe validates it's sibling c:\xodash\xonlinedash.xbe http://forums.xbox-scene.com/index.php?showtopic=289912&view=findpost&p=1905324 (c:\xodash\xonlinedash.xbe checks c:\xboxdash.xbe). If either fails, it throws an error.
This remains the case even if c:\xodash\xonlinedash.xbe is invoked directly via a retail XBL game!
eh hints that two c:\xboxdashdata.### folders are involved. AFAIK the only interesting file in that folder is the EasterEgg renamed .xbe (settings_adoc.xip). But since none of pertinent files described above live in the c:\xboxdashdata.### folders, I remain as curious as everyone regarding what eh has found.
Welcome back Pedro; I was concerned my quips about your earlier 'guess' (being the "lowest score") may have p'd you off. I certainly meant no disrespect and yours was in fact a very significant contribution ... being something this must avoid!
(BTW: I believe that "having no less compatibilities than UXE" infers it's none of the opportunities that I outlined, as such.)
Edit: additional qualifier...QUOTE(eh. @ Apr 29 2005, 07:33 AM)
Welcome back Pedro; I was concerned my quips about your earlier 'guess' (being the "lowest score") may have p'd you off. I certainly meant no disrespect and yours was in fact a very significant contribution ... being something this must avoid!
(BTW: I believe that "having no less compatibilities than UXE"
"and it might rival UXE" infers it's none of the opportunities that I outlined, as such.)
/me still waits till some "understandable" info is given
QUOTE(eh. @ Apr 29 2005, 03:33 PM)
Welcome back Pedro; I was concerned my quips about your earlier 'guess' (being the "lowest score") may have p'd you off.
Haha - not at all - I've been enjoying the 'build up' as much as everyone else.
QUOTE(PedrosPad @ Apr 29 2005, 05:26 PM)
Haha - not at all - I've been enjoying the 'build up' as much as everyone else.

and I'm still waiting for the climax
I must leave you all "at it" for quite a while, so will now indicate the crux of this and the (perplexed) challenge it embraces...
Maybe it was destiny that Pedro and I both just linked to that prophetic thread (me not so directly, of course)!
QUOTE(PedrosPad @ Apr 29 2005, 02:29 AM)
M$ don't need to scan your C drive, they simply pick a few details out of C:\xboxdash.xbe - it's version, date, certificate, etc. and compare then against the 'latest' Dash available on the XBL server.
If c:\xboxdash.xbe is an outdated retail MS Dash, it'll be updated.
so in cold booting it defines the update.xbe bootstrap as "not an old dash" and therefore doesn't update? as opposed to looking for "not the new dash" and updating? otherwise coldbooting would force a dash update which would error out because of the fonts and then no live....right?
QUOTE(PedrosPad @ Apr 29 2005, 02:29 AM)
Also, from D:5960 (the latest M$ Dash), the c:\xboxdash.xbe validates it's sibling c:\xodash\xonlinedash.xbe
http://forums.xbox-scene.com/index.php?showtopic=289912&view=findpost&p=1905324 (c:\xodash\xonlinedash.xbe checks c:\xboxdash.xbe). If either fails, it throws an error.
This remains the case even if c:\xodash\xonlinedash.xbe is invoked directly via a retail XBL game!
well...you figure ms would catch on sometime right?
QUOTE(PedrosPad @ Apr 29 2005, 02:29 AM)
eh hints that two c:\xboxdashdata.### folders are involved. AFAIK the only interesting file in that folder is the EasterEgg renamed .xbe (settings_adoc.xip). But since none of
pertinent files described above live in the c:\xboxdashdata.### folders, I remain as curious as everyone regarding what eh has found.
yeah, i was thinking one dash with an easter egg, other not...but the easter egg really doesn't effect the dash does it? so it's not like you'd really NEED the second dashdata folder...perhaps eh has found a way of totally overhauling the dash via the data files?! (i'd doubt it, but it's the best i can come up with...)
QUOTE(krayzie @ Apr 29 2005, 11:23 AM)
/me still waits till some "understandable" info is given

you're not the only one!
QUOTE(cmiz @ Apr 29 2005, 08:34 PM)
QUOTE(cmiz @ Apr 29 2005, 07:36 AM)
just a general question, how does MS know if you don't have an up to date dashboard? i'm assuming they don't scan your C drive to check the xboxdashdata.xxxx folder (else a lot of people would be in trouble) and if they did, coldbooting wouldn't work. they know when to update though, is it the size of the xboxdash file? just curious...
QUOTE(PedrosPad @ Apr 29 2005, 02:29 AM)
M$ don't need to scan your C drive, they simply pick a few details out of C:\xboxdash.xbe - it's version, date, certificate, etc. and compare then against the 'latest' Dash available on the XBL server.
If c:\xboxdash.xbe is an outdated retail MS Dash, it'll be updated.
so in cold booting it defines the update.xbe bootstrap as "not an old dash" and therefore doesn't update? as opposed to looking for "not the new dash" and updating? otherwise coldbooting would force a dash update which would error out because of the fonts and then no live....right?
On 2nd thoughts maybe it's details of c:\xodash\xonlinedash.xbe that determine if a Dash update is necessary (yeah, that kind'a makes sense
). But M$ certainly don't scan the C: drive to determine it, so you're right there.
.
With UXE and XBL, you must fully update and set up your XBL account ahead of installing UXE. Once UXE is installed, XBL retail games work fine, but the UXE exploit fonts prevent the XBL Console from functioning.
so if you just coldbooted into live every time after setting up your account and softmodding....would you ever need an update? because you'd never run the XO dash and it wouldn't actually stop to check if you're up to date unless you run the XO dash right?
or do i have the wrong idea?
OH SHIT, he's still alive?
Yes, I'm still breathing (*knocks on wood*)
Been busy with a bunch of RL stuff, it's real nice to see something (hopefully) new in this subforum.
I took "revival" into account (pre ude / uxe exploits working together with new). I hope that's not what he's shooting for as finger-mashing isn't my cup of tea (as it wouldn't prove to be "superior" to what we already have).
But anyways,
/me takes a peek at the readme file of one of our unreleased projects:
CODE
Required:
---------
- An xonlinedash.xbe file from MS dashboard version 4920. There are two
supported versions:
* Dashboard 4920 (0x17CDC100, UXE dash)
- xonlinedash.xbe has file size 1929216.
- file md5sum: 8da4d816604e9b9d5aa69d1fd395a48e
- works with all kernels (3944-5838) and all regions.
* Dashboard 4920 (0x1012A700)
- xonlinedash.xbe has the same file size 1929216
- file md5sum: ffd55eb62f21d1f00585dbf9d02a1503
- works with kernels 3944-5530 and all regions.
Close to it or not, this is very interesting eh? 
Anyone care to run a api logger on this xbe (uxe ver. with no fonts) to see what mr. rmenhal may have missed or intentionally kept from us 
-devz3ro
Good to see you back, devz3ro
does anybody KNOW what happened to rmenhal? Or did he give us some wonderful code, then vanish?
Either way, Eh's little riddle is very entertaining after such a calm xbe scene!
@devz3ro: welcome back Boss ... you got it! I have very little time right now, so briefly ...
Recall that you scene-released the necessaries re. UEEE ... I doubt rmenhal missed/kept anything (did he ever?) but he might not have had chance/inclination to look into the .xmv's ... he was shooting for the whole vision and I suspect he lost interest upon confirming M$ nix'd that.
My focus and abilities are narrower, so I've merely followed up on BluhDeBluh's prophecy ... no live console but it's direct booting with retail fonts too (and apparently optional startup .xmv's, haven't tried that yet).
Absolutely *crucially* my setup prevents dashupdate.xbe from nuking anything! update.xbe will have its fonts so apparently will work *if* the aforementioned "protection mechanism" doesn't impact it...
QUOTE(cmiz @ Apr 29 2005, 11:28 PM)
so if you just coldbooted into live every time after setting up your account and softmodding....would you ever need an update? because you'd never run the XO dash and it wouldn't actually stop to check if you're up to date unless you run the XO dash right?
or do i have the wrong idea?
I don't find that quite logical. It does somehow check some certificate stamps to see if an update is necesarry otherwise it should still be able to go live with a 4920 dash if you keep coldbooting. Maybe the kernel loads some of those stamps into memory for xbox live to check.
QUOTE(krayzie @ Apr 29 2005, 11:33 PM)
I don't find that quite logical. It does somehow check some certificate stamps to see if an update is necesarry otherwise it should still be able to go live with a 4920 dash if you keep coldbooting. Maybe the kernel loads some of those stamps into memory for xbox live to check.
i thought the same thing...but if they checked the xboxdash.xbe certificate, they'd be able to tell it wasn't the right file when coldbooting with UXE. perhaps they have a log in your live account somewhere? i mean...you can get onto live with a pretty much nuked C drive if you cold boot right? how would they know which "dash" you have then, seeing as you don't really have a dash when running UXE?
i don't use live so perhaps you need the xboxdashdata folder in which case they could probably tell which dash you had...but what if you renamed that folder to the newest dash? i just don't see how they'd check without being able to see that you're using UXE.
2...
----
QUOTE(eh. @ Apr 29 2005, 09:30 PM)
@devz3ro: welcome back Boss ... you got it! I have very little time right now, so briefly ...
Recall that you scene-released the necessaries re. UEEE ... I doubt rmenhal missed/kept anything (did he ever?) but he might not have had chance/inclination to look into the .xmv's ... he was shooting for the whole vision and I suspect he lost interest upon confirming M$ nix'd that.
My focus and abilities are narrower, so I've merely followed up on BluhDeBluh's prophecy ... no live console but it's direct booting with retail fonts too (and apparently optional startup .xmv's, haven't tried that yet).
Absolutely *crucially* my setup prevents dashupdate.xbe from nuking anything! update.xbe will have its fonts so apparently will work *if* the aforementioned "protection mechanism" doesn't impact it...
BTW: I've already confirmed it survives coldboots of these retails: SWT's bonus disc and HULK plus H2's XBL->dashupdate.xbe
...wow...
QUOTE(eh. @ Apr 30 2005, 12:32 AM)
BTW: I've already confirmed it survives coldboots of these retails: SWT's bonus disc and HULK plus H2's XBL->dashupdate.xbe
so basically its advantage is that it's updateable, correct? that's cool
anyone know anything more about my previous post regarding how MS knows when to update?
The certificate of the xboxdash.xbe isn't checked unless you attempt to access the Live Console AFAIK. I have coldbooted into a live enabled game with a completely wiped 'C' partition.
@cmiz:
Its primary advantage is that any .xbe requiring the real retail fonts runs (whereas UXE would FRAG).

Its secondary advantage is that it endures dashupdate.xbe without impact (whereas UXE would FRAG).
___
Re. "updates" here's how it seems to work... there are at least two kinds of updates, dashboard and game. Ahead of both, via XBL, the xonlinedash.xbe's certificate version number's verified with XBL's current version. For game updates, the verson attribute of default.xbe's also checked against XBL's current.
(Note1: this happens during connections to live, which mostly isn't during the boot process.)
(Note2: dashupdate.xbe's compare the version number of the xboxdash.xbe and the xonlinedash.xbe with their own version number.)
QUOTE(eh. @ Apr 29 2005, 10:32 PM)
2...
----
BTW: I've already confirmed it survives coldboots of these retails: SWT's bonus disc and HULK plus H2's XBL->dashupdate.xbe
i) For 1:1 backups of the above discs I anticipate that UXE and Ndure (codename was FUSE) would produce the same, successful results IFF they are both coupled with a "ShadowC implementation".
ii) For a non-"ShadowC implementation" then I think 1:1 backups of the above discs would (also) behave as per the following...
iii) Re. retail/original coldboots...
1) For the SWT bonus disc (SWTbd) movie:
With UXE, the box will FRAG.
With Ndure, the SWTbd's dashupdate.xbe is allowed to run but not do any damage! After that SWTbd's default.xbe runs successfully and its menu appears.
2) For the HULK disc 2 movie:
With UXE, the box will FRAG.
With Ndure, the HULK's default.xbe is allowed to run successfully and its menu appears.
3) For the Halo 2 game via attempted set up of a new XBL account:
With UXE, the box will FRAG.
With Ndure, Halo 2's dashupdate.xbe is allowed to run but not do any damage! After that the box quick-boots (IIRC) back to the menu.
4) For the Halo 2 game via attempted usage of the troubleshooter:
With both UXE and Ndure, the box will FRAG.
___
2...
QUOTE(Angerwound @ Apr 30 2005, 01:38 PM)
The certificate of the xboxdash.xbe isn't checked unless you attempt to access the Live Console AFAIK. I have coldbooted into a live enabled game with a completely wiped 'C' partition.
makes sense...so theoretically if you continue coldbooting, you'd never have to update your dash or anything, right? (unless MS decides to intentionally do something about that.)
QUOTE(eh. @ Apr 30 2005, 01:47 PM)
@cmiz:
Its primary advantage is that any .xbe requiring the real retail fonts runs (whereas UXE would FRAG).

Its secondary advantage is that it endures dashupdate.xbe without impact (whereas UXE would FRAG).
are there any multi game discs that are live enabled? because now you can coldboot those too. (you couldn't before correct? as you had to have the retail fonts or it would error out.)
QUOTE
makes sense...so theoretically if you continue coldbooting, you'd never have to update your dash or anything, right? (unless MS decides to intentionally do something about that.)
(Alas, there'd still be game updates; see below).
QUOTE
are there any multi game discs that are live enabled? because now you can coldboot those too. (you couldn't before correct? as you had to have the retail fonts or it would error out.)
Excellent point cmiz; there's at least one already (TopSpin+NCAA2005) and could be others. I wonder if any Live enabled demos might benefit too?
However, I suspect the biggest benefit would result from the update.xbe being operational for games. The Halo 2 updates are presumably having to be worked-around by most XBL softmodders currently!
(Due to its technique, I anticipate that XBL's game updates will work with Ndure!
)
ok, here i am after a little time away...(except in BST)
i've been real busy lately with exams and work 
eh sent me an email about this. sounds like something great that the whole softmodding community can appreciate. can't wait to test it out
Not being an XBL user myself, I wasn't aware they didn't work with UXE (no one's ever mentioned it
). If so, a useful improvement indeed for those who can benefit.
@atomiX&Pedro: thanks for the words of encouragement (and we'll all know at sometime, if not already).
QUOTE(wrayal @ Apr 22 2005, 08:35 AM)
/me wonders the point of announcing this in such a way
Anyway, cool to hear - guess there must be something cool and new

Let's hear it!

(/me knows change can be difficult to accept, especially of the paradigm.)
There's method in my madness. Time waits for one, no?
___
1...
eh: I'd figured there'd be at least some reason, one way or another ;p
Well, I've been following the thread closely (but not contributing anything :\). So....one more...anytime now....
(tbh, I was passed a package that contained that bit of readme posted earlier IIRC, so I have this feeling I know what is coming...)
Wrayal
This is sounding cooler everyday.. I wish I was at home with my xbox trying to fit these puzzle pieces together.. We definately needed something like this in this forum, I was getting bummed out having nothing but noob posts to reply to.. Thanks eh.. (Double meaning since I'm Canadian too..
)
You're welcome trigger. (Btw, I think Ndure has the potential to "beef CHUI up" even more!
)
The clock's gradually approaching "zero hour" (give or take a time zone) and the final stages of this process will then begin. Those will be:
A} the Ndure beta testing;
B} your (potentially superior) minds validating my rationale, which will provide...
C} the knowledge necessary to subsequently improve and/or try Ndure for yourselves.
However, Ndure's not the most significant point of the countdown (IMHO)! Does anyone know the "softmod happening" we've really all been gathered to remember?
QUOTE
However, Ndure's not the most significant point of the countdown (IMHO)! Does anyone know the "softmod happening" we've really all been gathered to remember?
hmm....
Edit: [colour|color] correction...
QUOTE(eh. @ May 2 2005, 10:43 AM - part)
However, Ndure's not the most significant point of the countdown (IMHO)! Does anyone know the "softmod happening" we've really all been gathered to remember?
lmao
QUOTE(eh. @ May 2 2005, 12:43 PM)
The clock's gradually approaching "zero hour" (give or take a time zone)
well hurry it up! we're getting impatient!!
QUOTE(eh. @ May 2 2005, 12:43 PM)
However, Ndure's not the most significant point of the countdown (IMHO)! Does anyone know the "softmod happening" we've really all been gathered to remember?
the wholesale sodomy of billy gates and his evil empire? no? i'll sit back down now...(are you referring to UD-eh and it's many contributions?)
QUOTE(eh. @ May 2 2005, 02:04 PM)
Edit: [
colour|
color] correction...
eh...i'm colorblind. makes no difference to me!
QUOTE
You're welcome trigger. (Btw, I think Ndure has the potential to "beef CHUI up" even more!
Sweet.. When I get home to fix that puppy I think I'm gonna make the XSelect an optional component as well.. Might as wel spend the time to give ppl all the options possible.. Any idea how much mem card space it will take to implement it?
QUOTE(triggernum5 @ May 2 2005, 03:25 PM)
Sweet.. When I get home to fix that puppy I think I'm gonna make the XSelect an optional component as well.. Might as wel spend the time to give ppl all the options possible.. Any idea how much mem card space it will take to implement it?
regarding memory card size....i've actually been dabbling in auto installer discs with lots of different softmod setups. that way, you're working with a 650 MB limit (or 4400 mb limit for a dvd) instead of the 8.
you could just have a memory card installer that installed a very stripped down version of UXE (heck, you wouldn't even need to install a dashboard as nkpatcher would load the DVD installer without one). from there you've got a lot more install options.
that's not particularly relevant to this thread, but could perhaps come in handy if it ended up being a rather beefy exploit. PM me i suppose if anyone is at all interested in doing something like that. (i'm sure it would be fairly easy to implement.)
compressed zip file of fonts will be around 4-5 mb I guess.. add 1mb of xboxdash.xbe and 2 mb of dashboard there.. I guess we can put it under 8MB with .rar..
I just meant the additional files eh is working on, my installer is sitting at roughly 7MB, but I could strip dvdx2 at a whim.. Perhaps this would allow me to strip UEEE as well, I don't know yet.. Regarding the softmod disc, I actually have my own that I use when the dvd drive in whatever box I'm modding will read it.. Some drives are a bitch, so I hope this will squeeze into 8MB..
The time is upon us: Let's Celebrate "rmenhal-day"! (May 3rd [and Beyond...])!
.
.
.
Next
dimension
uber
rmenhal
exploit
.
.
.
Beta testing is now underway ... 
QUOTE
However, Ndure's not the most significant point of the countdown (IMHO)! Does anyone know the "softmod happening" we've really all been gathered to remember?
Given the color change i found this (blue wasn't in ur sig)
QUOTE
Thanks for the idea and offer dudes but (IMO) this isn't package material eh. (I posted the steps above merely to assist others with trying the 5680 dash for themselves, and/or understanding the concept.)
But i would go for ROE if i where guessing
@Cmiz i softmod every box i do like that, memory card installer (just UXE/nkpatcher) and a simple installer CD containing a shadowc file and apps.
QUOTE(Cio @ May 3 2005, 12:40 AM)
@Cmiz i softmod every box i do like that, memory card installer (just UXE/nkpatcher) and a simple installer CD containing a shadowc file and apps.
yeah, me too....i was wondering if anybody wanted to make a generalized distro though. it seems enthusiasm is lackluster though so perhaps we'll just stick to memcard installers for the time being...
Hmz i think it would be nice to have an installer disk that can be used to either install on a chip/tsop box AND finish up a softmod. (edit: finish up my own UXE install or any exploit with a virtual C, a shadowc.img of 260 MB is included on the CD)
I made one for myself out of desperation.. but as i know evox files can't be hosted on xbins (if im wrong on this please point it out). It just installs avalaunch/dvd2xbox/xbmc/linksbox/emus and is only ~250 MB rarred
IF an installer using evox to copy files would still be hosted on xbins... could someone point out how i can "submit" this?
QUOTE(Cio @ May 3 2005, 07:04 AM)
Hmz i think it would be nice to have an installer disk that can be used to either install on a chip/tsop box AND finish up a softmod. (edit: finish up my own UXE install or any exploit with a virtual C, a shadowc.img of 260 MB is included on the CD)
I made one for myself out of desperation.. but as i know evox files can't be hosted on xbins (if im wrong on this please point it out). It just installs avalaunch/dvd2xbox/xbmc/linksbox/emus and is only ~250 MB rarred
IF an installer using evox to copy files would still be hosted on xbins... could someone point out how i can "submit" this?
i actually use unleashx because i've come to like it a little better and also you can rar things.
i think basically the deal with xbins is that they won't directly host evox releases...but if a distro just happens to include the dash, they're not going to refuse it. i think they're going for the principle of the thing...not trying to be assholes, y'know?
@Cio: excellent point about the green (and the HULK exploit). However, on this occasion it was re. the X-S connection (and the daily countdown ending on May 3).
Beta status... it's taken us longer than anticipated to establish the foundations, but everything's in place now. ("Thank you SlaYer!" for most recently having something unexpected!)
There will be two types of testers - the existing ("UEEE pioneers") plus an "above board" group.
The latter includes you if you're interested. No need to contact me; just visit the thread, share your ideas and see what evolves!
Knowing what the original testers already had (and didn't) is enough to begin with...
wait a sec....i'm really confused....
QUOTE(eh. @ May 3 2005, 10:08 PM)
There will be two types of testers - the existing ("http://forums.xbox-scene.com/index.php?showtopic=349585 pioneers") plus an "above board" group.
i remember that thread...but i thought the general conclusion was that it wasn't really anything revolutionary to the scene. (except for krayzie's SCEEE switcher, which was awesome, but most people favored coldbooting anyways). have you modified this exploit in some way?
QUOTE(eh. @ May 3 2005, 10:08 PM)
Knowing what the original testers already had (and didn't) is enough to begin with...

i have a copy of a UEEE setup that i can install...and i remember using it....but i don't really see what i'm supposed to be doing or looking for. is this a "make your own softmod" or do you actually have a new exploit and you're just making us figure it out? what i mean is: is this basically a variation on UEEE?
your confused...
I'm excited, whats this all about?
QUOTE(eh. @ May 3 2005, 10:08 PM)
Knowing what the original testers already had (and didn't) is enough to begin with...

what new dash updates have occured since the UEEE release? i don't really know what else this could be (nor what was in slayers...are you talking about the current release or an older version?)
is http://forums.xbox-scene.com/index.php?showtopic=289912&view=findpost&p=1901400 relavent at all? perhaps http://forums.xbox-scene.com/index.php?showtopic=289912&view=findpost&p=1902392 coupled with the uber xonlinedash? am i hot? cold? (though not as cold as you guys up north! that's for sure!
)
QUOTE(NICNAC @ May 3 2005, 11:18 PM)
your confused...
I'm excited, whats this all about?
most of us are about as in the dark as you...all i can say is....read up!
edit: tired, not making as much sense as i'd like...and posting wrong links to things...
@cmiz: thank you (and others) for bearing with me. Re. the following, "A}" commenced yesterday and now "B}" has:
QUOTE(eh. @ May 2 2005, 10:43 AM - part)
A} the Ndure beta testing;
B} your (potentially superior) minds validating my rationale, which will provide...
C} the knowledge necessary to subsequently improve and/or try Ndure for yourselves.
Re. "is this basically a variation on UEEE", ironically it's the opposite - remember that confusing readme file? That was about the "uber rmenhal exploit"!
Re. 'current or older', please see my related wording.
(Re. tired, me too, so I'll review the links after a good night's
))
Hmm...yes, this was the one I saw a while ago it would seem. Though....I have absolutely no idea whether or not eh wants everyone to know....I'm going to keep schtum. Just my own but of advice: everything you need, I believe is in existence - look closely at the UEEE thread....
Wrayal
QUOTE
Re. "is this basically a variation on UEEE", ironically it's the opposite - remember that confusing readme file?
So the opposite.. no live dash access? kinda like
QUOTE
I noticed that xonlinedash.xbe will create a symbolic link C:\xodash -> Y: in case the file C:\xodash\Xbox.xtf exists. This means that it will then look fonts first in C:\xodash\fonts and then in C:\xodash.
So, either
1) Copy the older fonts usually found in C:\ to C:\xodash\. Note that dash 5659+ will checksum the files so you do need to use the old fonts.
or
2) Create the directory C:\xodash\fonts and copy the newer good fonts usually found in C:\fonts there. Then create a dummy file (0 bytes will do) to C:\xodash\Xbox.xtf (you could also copy the old fonts to C:\xodash in case you wanted to waste disk space.)
I don't have the latest 5960 dash so I don't know if this has been removed.
That, only now using hacked fonts in C:\xodash\fonts, would theoraticly allow for a live tab that boots habibi signed code. (NKpatcher)
), because they all employ the update.xbe exploit opportunity that he discovered.)
When rmenhal shared his find (in that thread) he was determining whether it would allow us to use the hacked fonts (pathed via C/fonts) and simultaneously provide full XBL support (pathed via /C/xodash/fonts)? Alas, it didn't because M$ had closed the hole in 185EAD00. 
End of story? Nope; notice also in that thread that BlurDeBlur immediately suspected that hacked fonts could use the new path instead (shortly after which, rmehnal produced them re. the regular and uber 4920 xonlinedash.xbe).
This uber rmenhal exploit ('ure') provided the same features as UXE and the potential for others, because for the first time it would be possible for a direct booting exploit to have simultaneous retail fonts support (plus maybe some "additional coolness" via XMV files)!
However, it wasn't released (until devz3ro's UEEE scene-release, which uses the same fonts...) and I soon learned what I'M HOPING was the ONLY reason.
dashupdate.xbe was no longer automatically prohibited (if retail fonts were in place) and would reset the dashboard to retail state!
Hmm, but (/me ponders) what if there was another way to prohibit dashupdate.xbe from clobbering the softmod's setup - then we could maybe take this opportunity to another level?
Ndure is a method, that uses the 'ure' as the start up (bootstrap) files plus takes it into the next dimension (to overcome the dashupdate.xbe issue)!
_______
I must go to work now; you have the necessary info. plus great minds, so maybe you'd like to brainstorm how Ndure could do that...
(Take full backups and ensure your box is currently chip, tsop, gamesave or swap recoverable ... just in case!)
QUOTE(eh. @ May 4 2005, 03:08 PM)
Hmm, but (/me ponders) what if there was another way to prohibit dashupdate.xbe from clobbering the softmod's setup - then we could maybe take this opportunity to another level?
Ndure is a method, that uses the 'ure' as the start up (bootstrap) files plus takes it into the next dimension (to overcome the dashupdate.xbe issue)!
One known alternative, but very clunky, way to prevent a Dashboard update is to completely fill up the C drive. This causes the dashupdate to abort since it requires some working space.
It be nice to think you'd come up with a cleverer method than that?
im in over my head (most likely) or i got at least a part of the awnser.
Write protect essential files by using linux to place em.
Either that or the "timestamp and version values" are being fucked with enuff to make the dashupdate think it doesn't need to do anything, no matter what date it would be.
ohwk nvm i lost my point.
Edit: apologies to BluhDeBluh - spelling correction...
QUOTE(eh. @ May 4 2005, 07:08 AM - part)
End of story? Nope; notice also in that thread that BluhDeBluh immediately suspected that hacked fonts could use the new path instead (shortly after which, rmehnal produced them re. the regular and uber 4920 xonlinedash.xbe).
QUOTE(PedrosPad @ May 4 2005, 07:40 AM)
One known alternative,
but very clunky, way to prevent a Dashboard update is to completely fill up the C drive. This causes the dashupdate to abort since it requires some working space.
It be nice to think you come up with a cleverer method than that?
No I didn't (that's exact what I've done) and is one of the reasons for this validation of my rationale (and opportunity for folks to subsequently improve upon it).
______
Footnote: the file I'm filling it with is shadowc.img 
QUOTE(eh. @ May 4 2005, 03:48 PM)
QUOTE(PedrosPad @ May 4 2005, 07:40 AM)
One known alternative,
but very clunky, way to prevent a Dashboard update is to completely fill up the C drive. This causes the dashupdate to abort since it requires some working space.
It be nice to think you come up with a cleverer method than that?
No I didn't (that's exact what I've done) and is one of the reasons for this validation of my rationale (and opportunity for folks to subsequently improve upon it).
np - Heck, if it works run with it 
Sounds like excellent work eh.
Well done for realising what the sum of the parts equalled. 
Great. Now at least someone will make a xbox app that creates a shadowc.img from empty space instead of the whole partition or a dummyfile.
I've wanted something like that for a while...
i have the right idea...but for some reason i'm having problems getting it to run. i'm using kernel specific fonts, i've tried 61 and 71. i've tried loading the fonts from xodash, xodash\fonts, and xodash\fonts with a zero length xbox.xtf, but it always hang at the big x screen (so i think it's a font issue). any ideas?
QUOTE(eh. @ May 4 2005, 09:48 AM)
Footnote: the file I'm filling it with is shadowc.img

what size img file are you using? i currently use a 300 mb version for my uxe setups, the dash takes up about 170 mb, and the C drive is 500 mb. so 500-300-170= 30mb. is that enough for a dash update to occur? or would i be alright with that?
i suppose an alternative to just filling up the c drive would be nice...but i usually hide shadowc.img on C anyways so it really doesn't make much difference in that respect. i agree that a shadowc.img makes that could make a file of the correct size would be nice...but as blackwar showed in his installer, we could just include the correct size shadowc.img already formatted (blank) and zipped up to a very small size.
QUOTE(cmiz @ May 4 2005, 04:23 PM)
i have the right idea...but for some reason i'm having problems getting it to run. i'm using kernel specific fonts, i've tried 61 and 71. i've tried loading the fonts from xodash, xodash\fonts, and xodash\fonts with a zero length xbox.xtf, but it always hang at the big x screen (so i think it's a font issue). any ideas?
xonlinedash.xbe exploits use their own specific fonts.
QUOTE
This uber rmenhal exploit ('ure') provided the same features as UXE and the potential for others, because for the first time it would be possible for a direct booting exploit to have simultaneous retail fonts support (plus maybe some "additional coolness" via XMV files)!
However, it wasn't released (until devz3ro's UEEE scene-release, which uses the same fonts...)
QUOTE(PedrosPad @ May 4 2005, 10:34 AM)
xonlinedash.xbe exploits use their own specific fonts.
i don't understand...i have UEEE working. i type in <<Eggs(B)ox>> and it loads up just fine....but if i then try renaming that settings_adoc.xip file (which is the uber xonlinedash.xbe, right?) to C:\xboxdash.xbe, it hangs.
am i confused here? am i using the wrong files? i thought it was basically the same setup as UEEE except that instead of being used as settings_adoc, it's used as a bootstrap.
edit: and i'm using the fonts for UEEE, i assumed those were the right ones. are they not?
Hello I am wondering if that Cheeseburger Helmet picture is of triggernum5 oh and cmiz that happened to me before I figured out what rmenhal meant about the media folder oh and the beta testing is fun.
QUOTE(eh. @ May 4 2005, 07:08 AM - mostly)
rmenhal discovered a new way to exploit the M$ dash (so it really
is rmenhal's exploit)!
(Imo UDE/2/UXE are Pedro's (

), because they all employ the update.xbe exploit opportunity that
he discovered.)
When rmenhal shared his find (in that thread) he was determining whether it would allow us to use the hacked fonts (pathed via C/fonts) and simultaneously provide full XBL support (pathed via /C/xodash/fonts)? Alas, it didn't because M$ had closed the hole in 185EAD00.

End of story? Nope; notice also in that thread that BlurDeBlur immediately suspected that hacked fonts could use the new path instead (shortly after which, rmehnal produced them re. the regular and uber 4920 xonlinedash.xbe).
This uber rmenhal exploit ('ure') provided the same features as UXE and the potential for others, because for the first time it would be possible for a direct booting exploit to have simultaneous retail fonts support (plus maybe some "additional coolness" via XMV files)!
However, it wasn't released (until devz3ro's UEEE scene-release, which uses the same fonts...) and I soon learned what I'M HOPING was the ONLY reason.

dashupdate.xbe was no longer automatically prohibited (if retail fonts were in place) and would reset the dashboard to retail state!
Hmm, but (/me ponders) what if there was another way to prohibit dashupdate.xbe from clobbering the softmod's setup - then we could maybe take this opportunity to another level?
Ndure is a method, that uses the 'ure' as the start up (bootstrap) files plus takes it into the next dimension (to overcome the dashupdate.xbe issue)! For those interested, here's the beta test outline...
(Take full backups and ensure your box is currently chip, tsop, gamesave or swap recoverable ... just in case!)
To implement Ndure, backup everything (as per the usual guidelines,
especially the C-partition!) and then do the following:
Confirm that you have a backup of UEEE's files plus your 185ead00
dashboard and former pre-live dashboard (i.e. 4817 or earlier).
If you don't have ALL of these available, then DO NOT PROCEED!!
(Until you have recovered the required components below.)
ftp into your Xbox (with full administrative rights) and ...
a. format the REAL C-partition (or delete all of its contents)
b. copy 185ead00's XOdash folder and all its contents to /C/XOdash
c. Copy UEEE's ernie.xtf to /C/XOdash/ernie.xtf
(this .xtf MUST be copied into place before the one that follows)
d. Copy UEEE's Xbox.xtf to /C/XOdash/Xbox.xtf
(use the one for your kernel version [or the generic one if you're
unsure] but it must be named Xbox.xtf)
e. copy UEEE's media folder and all its contents to /C/media
(which *optionally* includes zero, one or two "start up" .xmv files
[live.xmv | liveloop.xmv])
f. copy UEEE's xonlinedash.xbe to /C/xboxdash.xbe
(this is the C-partition's primary start up file and MUST be named
xboxdash.xbe)
g. copy pre-live dash's Xbox Book.xtf to /C/Xbox Book.xtf
(this provides retail disc support)
h. copy pre-live dash's Xbox.xtf to /C/Xbox.xtf
(this provides retail disc support)
i. create an empty directory named /C/fonts.du
(this serves as an important reminder reminder NOT to have a
"/C/fonts" directory!)
j. create an empty directory named /C/xboxdashdat.du
(this serves as an important reminder NOT to have a
"/C/xboxdashdatA.WHATEVER" directory!)
k. copy any files that YOU need in the C-partition to support the
E:/default.xbe (or equiv.) referenced by the UEEE fonts
l. make sure you have all files that YOU need in the other partitions
to support the E:/default.xbe (or equiv.) referenced by the UEEE fonts
m. create a huge file (ideally shadowc.img) that consumes all of the
remaining space on the C-partition, except for 1Mb!
(you can actually leave up to 1.2Mb free space on the C-partition,
BUT ANY MORE CAN BE A RISK!)
... re-start the Xbox (and enjoy Ndure)!
some questions:
1.since I dont have that ancient dash.. and it seems like the fonts only serves to boot retail games which I am not booting at this time.. can I proceed without this two fonts?
2. Does ndure boot startup .xmv?.. what should be the name of .xmv so that ndure boots it at launch?
3. what is teh purpose of filling up that space?..
QUOTE
1.since I dont have that ancient dash.. and it seems like the fonts only serves to boot retail games which I am not booting at this time.. can I proceed without this two fonts?
yes, but then you may as well be using uxe. check slayers for fonts.
QUOTE
2. Does ndure boot startup .xmv?.. what should be the name of .xmv so that ndure boots it at launch?
no, the .xmv fles are optional.
QUOTE
3. what is teh purpose of filling up that space?..
dashupdate.xbe fails cuz there is no room for the update.
and i can confirm the above method works on a k5101
and btw thx to eh, rmenhal, and whoever else helped for this new expliot!
@kingroach:
Re. 1 - get the fonts (else you'll get FRAG's from some .xbe's)
(IMPORTANT: only use the fonts from /C/ (*NOT* /c/fonts) else some .xbe's will FRAG)
Re. 2 - the xonlinedash.xbe (that's now the xboxdash.xbe) plays them if they're in /C/media (named live.xmv and/or liveloop.xmv) ... this isn't tested yet though ... they're optional (not required)
Re. 3 - to stop dashupdate.xbe resetting the dash back to retail
(P.S. thanks scimitar116
)
QUOTE(eh. @ May 5 2005, 03:48 AM)
@kingroach:
Re. 1 -
get the fonts (else you'll get FRAG's from some .xbe's)(IMPORTANT: only use the fonts from /C/ (*NOT* /c/fonts) else some .xbe's will FRAG)Re. 2 - the xonlinedash.xbe (that's now the xboxdash.xbe) plays them if they're in /C/media (named live.xmv and/or liveloop.xmv) ... this isn't tested yet though ... they're optional (not required)
Re. 3 -
to stop dashupdate.xbe resetting the dash back to retail(P.S. thanks scimitar116

)
np 
and also, im sure this has been thought of 100 times, but is it possible to exploit the .xmv files in a way similar to how .mp3 and .jpeg files are exploited?
edit: are there crc32\md5 checks on the .xmv files? if not, even if they are unexploitable, you could put your own vids in.
I am currently building patchers to convert the fonts as we speak on a very slow computer.. With any luck tomorrow morning they will be available.. Without luck they will hopefully be done later that day..
QUOTE
Hello I am wondering if that Cheeseburger Helmet picture is of triggernum5
Edit: I weigh 120lbs.. The cheeseburger is heavier than I am..
@scimitar116: http://forums.xbox-s...dpost&p=1902392
@triggernum5: awesome - thanks
Woah...I was right for once ;p
It's a nice exploit - nice one eh. I'd certainly use it if it weren't for the fact that my box is now chipped etc.
Wrayal
Looks nice. But this new version loads directly into Nkpatcher, or your
modded setup, is there anyone to disable it from booting directly to
bring you to a MS dash (unmodded) and then "trigger" it. I like UEEE
switching method, just wish it was faster (no keystokes).
Ehm please don't bitch at me.. but all thats new is that u can now boot retail disks that call on the fonts (anyone care to name em?) and play on live with those disks.
If anyone can point out to me what games are involved.. i would love to know since this seems to have little to no advantage over current exploits. Esp since the Live dash doesn't work (AFAIK)
Oh, i REALLY need to add i love to see new develepments in the softmod scene and my god am i a happy camper knowing M$ is getting ass raped on the spot. You have my many, MANY thanks and love.
If anybody needs help finding pre-live fonts for ndure I have made some 'comments' regarding the subject on my AGI/CHUI webpage.
Apparently 64MB of ram on a P66 isn't enough to create a patch to convert the live fonts to the pre-live fonts.. Sorry for the 'convenience'
..
Edit: Cio, this might be of great value to some ppl.. And personally I'd love to see more interesting tactics develop even if they're inferior to modern exploits.. Livens the forum up.. Better than explaining how to get a gamesave on a memory card all day long..
what exactly is needed to create a patch?.. I have plenty of computing power..
thnx for the fonts man..
knock yourself out, I pm'ed you with a link to a freeware tool..
working on those.. xbox.xtf is 50% done..
the files matches exactly in my xbox's C:\ root fonts.. but my dash is 5659..
We crc'd the pre-live/post-live fonts last night.. There are only 2 sets..
Lemme know when you're done, I'll give you an address to upload them to for hosting..
QUOTE(eh. @ May 4 2005, 07:19 PM)
For those interested, here's the beta test outline...
(Take full backups and ensure your box is currently chip, tsop, gamesave or swap recoverable ... just in case!)To implement Ndure, backup everything (as per the usual guidelines,
especially the C-partition!) and then do the following:
Confirm that you have a backup of UEEE's files plus your 185ead00
dashboard and former pre-live dashboard (i.e. 4817 or earlier).
If you don't have ALL of these available, then DO NOT PROCEED!!
(Until you have recovered the required components below.)
ftp into your Xbox (with full administrative rights) and ...
a. format the REAL C-partition (or delete all of its contents)
b. copy 185ead00's XOdash folder and all its contents to /C/XOdash
c. Copy UEEE's ernie.xtf to /C/XOdash/ernie.xtf
(this .xtf MUST be copied into place before the one that follows)
d. Copy UEEE's Xbox.xtf to /C/XOdash/Xbox.xtf
(use the one for your kernel version [or the generic one if you're
unsure] but it must be named Xbox.xtf)
e. copy UEEE's media folder and all its contents to /C/media
(which *optionally* includes zero, one or two "start up" .xmv files
[live.xmv | liveloop.xmv])
f. copy UEEE's xonlinedash.xbe to /C/xboxdash.xbe
(this is the C-partition's primary start up file and MUST be named
xboxdash.xbe)
g. copy pre-live dash's Xbox Book.xtf to /C/Xbox Book.xtf
(this provides retail disc support)
h. copy pre-live dash's Xbox.xtf to /C/Xbox.xtf
(this provides retail disc support)
i. create an empty directory named /C/fonts.du
(this serves as an important reminder reminder NOT to have a
"/C/fonts" directory!)
j. create an empty directory named /C/xboxdashdat.du
(this serves as an important reminder NOT to have a
"/C/xboxdashdatA.WHATEVER" directory!)
k. copy any files that YOU need in the C-partition to support the
E:/default.xbe (or equiv.) referenced by the UEEE fonts
l. make sure you have all files that YOU need in the other partitions
to support the E:/default.xbe (or equiv.) referenced by the UEEE fonts
m. create a huge file (ideally shadowc.img) that consumes all of the
remaining space on the C-partition, except for 1Mb!
(you can actually leave up to 1.2Mb free space on the C-partition,
BUT ANY MORE CAN BE A RISK!)
... re-start the Xbox (and enjoy Ndure)!
(As kingroach found, the pre-live fonts may already be in your /C/ ... dashupdate.xbe doesn't delete the old [legacy] fonts from the root.)
Just one thing - I guess you still need to cold boot any games you want to plasy on live yeah? I actually used this hack to boot linux, and hence wanted a way to boot ONLY retail or linux. So, I actually used the dualbootretail.xbe. My personal preference for ndure would be this dual boot - open -> retail dash etc. Meanwhile, closed boot -> nkpatcher etc. Would this allow you to run live? just wondering - I have no way to test, and of course my reasons for doing this were somewhat different to (most of?) yours ;p
Wrayal
NO! It would appear to be so, but you would get banned.. Font exploits patch the public key regardless of whether nkpatcher loads or not.. And since no nkpatcher, no live blocking, therefore ban..
"dualbootretail.xbe"
Unpatches, loads ms dash, which loads true fonts due to the alternate font booting path of the xbe being hacked 
Wrayal
QUOTE(wrayal @ May 5 2005, 08:59 PM)
"dualbootretail.xbe"
Unpatches, loads ms dash, which loads true fonts due to the alternate font booting path of the xbe being hacked

Wrayal
correct me if im outta line asking this, but:
wrayal, where can i get my hands on that 'dualbootretail.xbe'? sounds like fun...
or were you just saying something like that should be created.
i didnt think 'unpatching' was possible for the xbox bios... dont know why lol.
Hello I wonder if you are having as much fun with the beta testing as I am now oh and I hope others can as well
oh and so if we do not already have something then we should remember that the usual places is what the rules allow.
I can see being able to unpatch the kernel, but does it load xboxdash as a different filename? Cause that wouldn't exactly be a retail kernel, and if it doesn't it will just end up reloading the ndure bootstrap..
if anyone dont have old font file.. here is a patch.. put your 5659 dash's xbox.xtf and xbox book.xtf into any folder ( both files should be in one folder)..and then run the patch.
http://www.amarshona...om/dl/patch.rar
To let ppl know, that patch will work with any fonts from 4920 to 5960.. To split up the bandwidth usage here is another link that should be up and working in 2 hours perhaps.. (Damn rural dialup:) )
http://triggernum5.servebeer.com/ndure/patch.rar
Edit: The link isn't on dialup, don't worry..
QUOTE(Cio @ May 4 2005, 07:40 AM - part)
Write protect essential files by using linux to place em.

I don't suppose there's a way for us to prevent dashupdate.xbe deleting a specific directory and its contents is there?
QUOTE(garyopa @ May 5 2005, 06:34 AM)
Looks nice. But this new version loads directly into Nkpatcher, or your modded setup, is there anyone to disable it from booting directly to bring you to a MS dash (unmodded) and then "trigger" it. I like UEEE switching method, just wish it was faster (no keystokes).
I suspect we could do it with 17cdc100 if the answer to my preceding question was "Yes" (but I doubt it'd provide a working and/or safe XBL platform though).
Edit - clarification: we'd need to stop dashupdate.xbe deleting xboxdashdata.17cdc100 (and its contents) though.
cio had a good idea...but the xboxhdm bug only does that to the E drive....if somebody knows WHY that bug occurs, they could possibly make a distro that would disable writing to ALL files written by it...no idea how that would work out though.
QUOTE(wrayal @ May 5 2005, 12:36 PM - hmm)
(That "one thing" seems to be "everything"!
)
Similarly, if we could find a way to stop dashupdate.xbe deleting xboxdashdata.185ead00 (and its contents) I suspect your 'preference' might be achieveable, but there'd be no Live console...
(Note: I'm trusting that "dualbootretail.xbe" suitably facilitates this magic, especially re. it not leaving any trace behind that XBL could find!)
QUOTE(eh. @ May 5 2005, 09:04 PM - questionable part!)
if we could find a way to stop dashupdate.xbe deleting xboxdashdata.185ead00 (and its contents)
Actually, I don't know if it would delete that particular instance, since it's the current XBL version ... I guess it might depend on how dashupdate.xbe examines xboxdash.xbe (which would be dualbootretail.xbe in this case) et al.
ROFL. If anyone can find the original dualboot thread, this dualbootretail.xbe is in there. (Trust me, I've had this hack up and running ;p)
yeah, no live console I'd guess (it's ages since I've done any of this, but IIRC it remaps and does an absolute path). There is one option, albeit somewhat complex. Setup shadowC type system. Let live console boot, then remove all the patches (find a kernel call it doesnt make until after it has loaded fonts, and stick in a 'removal' hook there).
Live access? I'd doubt it, but maybe. The kernel unpatching is simple - apply the XOR used for the habibi key again ;p
Wrayal
QUOTE(eh. @ May 4 2005, 07:19 PM)
For those interested, here's the beta test outline... :popcorn:
(Take full backups and ensure your box is currently chip, tsop, gamesave or swap recoverable ... just in case!)To implement Ndure, backup everything (as per the usual guidelines,
especially the C-partition!) and then do the following:
Confirm that you have a backup of UEEE's files plus your 185ead00
dashboard and former pre-live dashboard (i.e. 4817 or earlier).
If you don't have ALL of these available, then DO NOT PROCEED!!
(Until you have recovered the required components below.)
ftp into your Xbox (with full administrative rights) and ...
a. format the REAL C-partition (or delete all of its contents)
b. copy 185ead00's XOdash folder and all its contents to /C/XOdash
c. Copy UEEE's ernie.xtf to /C/XOdash/ernie.xtf
(this .xtf MUST be copied into place before the one that follows)
d. Copy UEEE's Xbox.xtf to /C/XOdash/Xbox.xtf
(use the one for your kernel version [or the generic one if you're
unsure] but it must be named Xbox.xtf)
e. copy UEEE's media folder and all its contents to /C/media
(which *optionally* includes zero, one or two "start up" .xmv files
[live.xmv | liveloop.xmv])
f. copy UEEE's xonlinedash.xbe to /C/xboxdash.xbe
(this is the C-partition's primary start up file and MUST be named
xboxdash.xbe)
g. copy pre-live dash's Xbox Book.xtf to /C/Xbox Book.xtf
(this provides retail disc support)
h. copy pre-live dash's Xbox.xtf to /C/Xbox.xtf
(this provides retail disc support)
i. create an empty directory named /C/fonts.du
(this serves as an important reminder reminder NOT to have a
"/C/fonts" directory!)
j. create an empty directory named /C/xboxdashdat.du
(this serves as an important reminder NOT to have a
"/C/xboxdashdatA.WHATEVER" directory!)
k. copy any files that YOU need in the C-partition to support the
E:/default.xbe (or equiv.) referenced by the UEEE fonts
l. make sure you have all files that YOU need in the other partitions
to support the E:/default.xbe (or equiv.) referenced by the UEEE fonts
m. create a huge file (ideally shadowc.img) that consumes all of the
remaining space on the C-partition, except for 1Mb!
(you can actually leave up to 1.2Mb free space on the C-partition,
BUT ANY MORE CAN BE A RISK!)
... re-start the Xbox (and enjoy Ndure)!
(If my understanding of wrayal's setup and info. is entirely correct, it seems that Ndure can be supplemented to provide tray-state {Softmod|Retail} selection at start up [due to Ndure's simultaneous fonts support when the box boots]!)
This post has been edited by eh.: May 6 2005, 12:10 PM
eh: got it in one. Sorry, I've never really explained a hack before, and it hadn't occured to me how obscure my references were.
Essentially, yes. UEEE xbe loads
Hacked by fonts -> XOR to habibi & boot tray-checker
Tray closed -> NKPatcher loads
Tray open -> unpatch habibi, original MS dash loads, totally unhacked
^^Latter is possible due to xboxdash loading C:\fonts, then C:\, while UEEE xbe loads \xodash\fonts, then \xodash IIRC
Wrayal
QUOTE(cmiz @ May 5 2005, 09:01 PM)
cio had a good idea...but the xboxhdm bug only does that to the E drive....if somebody knows WHY that bug occurs, they could possibly make a distro that would disable writing to ALL files written by it...no idea how that would work out though.
When dashupdate.xbe runs it deletes the /C/fonts directory and /C/xboxdashdata.whatever directory BEFORE staging the new dash files (via xboxdashdat.du initially).
The latter step is where Ndure intervenes (re. insufficient disk space) and had either or both of those two directories existed prior to that, they no longer would (see footnote).
Consequently, we likely need to figure out a way to stop /C/xboxdashdata.whatever (and its contents) being deleted too...
_______
Footnote: it's yet to be determined whether 185ead00's an exception to this with Ndure, but I doubt it would be (so I suspect wrayal's setup would be equally at risk)...
This post has been edited by eh.: May 6 2005, 03:32 PM
does linux/windows read only permission works on xbox?..
Nope, I've tried file permissions before.. I'm going to see if I can determine what makes E:\ special.. I will most likely fail though..
I think it formats E:\ with different cluster size or something..
IIRC, the reason you get read only stuff with linux is slightly different - the original fatx support had 0xfffffffd as it's EOF character, when it should have be 0xffffffff (or something similar). To the best of my knowledge, the xbox disliked this, and effectively couldn't write it...I did this to my C drive once :\ -> I'm pretty sure it ain't E: only.
BTW, I just had a quick look for the original dualboot thread, but couldn't find it. It'd be interesting, though I'm not sure how much benefit it brings.
what dualboot thread? maybe this post can be of any assistance to you
Ah, got it in one - thanks.
Yeah, it's the closed-retail.xbe from there. It was an odd thing to include at the time as there was no obvious way to use it - perhaps rmenhal had even more foresight than we though ;p
(NB, I cannot actually check on this computer, but I believe that is the correct thread/post/whatever)
Wrayal
the closed retail is just as the open retail except for the fact it boots to the msdash with tray closed instead of open. the term "retail" is a bit misleading though since in fact the xbox is not in a retail state at that point.
How so? I mean, of course, then files on the HD are in non-retail places, but other than that, it seemed to work as retail for me.
I mean, the fonts XOR the key, this XORs it back, then runs the ms dash, but whatever, that wasn't my original use for it ;p
God, I need access to both my xbox and a non-school computer so I can actually fiddle with this stuff again 
Wrayal
it xors nothing back. it was just set to load a hexed msdash at the time. the key stays altered.
Maybe this section of Closed-Retail.asm is what wrayal's referring to?
CODE
;-------------------------------------------------------------------------------
; This routine modifies the habibi public key back to MS public key.
;-------------------------------------------------------------------------------
Definitely not the one I used then - I am certain the ver I used unpatched then launched the msdash. I'll see if I can dig it up, otherwise, I'd guess it's a trivial patch for some around here ;p
Wrayal
QUOTE(eh. @ May 6 2005, 05:28 PM)
Maybe this section of Closed-Retail.asm is what wrayal's referring to?
CODE
;-------------------------------------------------------------------------------
; This routine modifies the habibi public key back to MS public key.
;-------------------------------------------------------------------------------
damnit. Why didn't I notice that before. If that works it could be quite usefull.
QUOTE(eh. @ May 4 2005, 07:19 PM)
For those interested, here's the beta test outline...
(Take full backups and ensure your box is currently chip, tsop, gamesave or swap recoverable ... just in case!)To implement Ndure, backup everything (as per the usual guidelines,
especially the C-partition!) and then do the following:
Confirm that you have a backup of UEEE's files plus your 185ead00
dashboard and former pre-live dashboard (i.e. 4817 or earlier).
If you don't have ALL of these available, then DO NOT PROCEED!!
(Until you have recovered the required components below.)
ftp into your Xbox (with full administrative rights) and ...
a. format the REAL C-partition (or delete all of its contents)
b. copy 185ead00's XOdash folder and all its contents to /C/XOdash
c. Copy UEEE's ernie.xtf to /C/XOdash/ernie.xtf
(this .xtf MUST be copied into place before the one that follows)
d. Copy UEEE's Xbox.xtf to /C/XOdash/Xbox.xtf
(use the one for your kernel version [or the generic one if you're
unsure] but it must be named Xbox.xtf)
e. copy UEEE's media folder and all its contents to /C/media
(which *optionally* includes zero, one or two "start up" .xmv files
[live.xmv | liveloop.xmv])
f. copy UEEE's xonlinedash.xbe to /C/xboxdash.xbe
(this is the C-partition's primary start up file and MUST be named
xboxdash.xbe)
g. copy pre-live dash's Xbox Book.xtf to /C/Xbox Book.xtf
(this provides retail disc support)
h. copy pre-live dash's Xbox.xtf to /C/Xbox.xtf
(this provides retail disc support)
i. create an empty directory named /C/fonts.du
(this serves as an important reminder reminder NOT to have a
"/C/fonts" directory!)
j. create an empty directory named /C/xboxdashdat.du
(this serves as an important reminder NOT to have a
"/C/xboxdashdatA.WHATEVER" directory!)
k. copy any files that YOU need in the C-partition to support the
E:/default.xbe (or equiv.) referenced by the UEEE fonts
l. make sure you have all files that YOU need in the other partitions
to support the E:/default.xbe (or equiv.) referenced by the UEEE fonts
m. create a huge file (ideally shadowc.img) that consumes all of the
remaining space on the C-partition, except for 1Mb!
(you can actually leave up to 1.2Mb free space on the C-partition,
BUT ANY MORE CAN BE A RISK!)
... re-start the Xbox (and enjoy Ndure)!
.
.
.QUOTE(krayzie @ May 6 2005, 09:33 AM)
damnit. Why didn't I notice that before. If that works it could be quite usefull.
Heh, took me a sec to see why you always paste things like that. Now I see. Well, thankfully that routine is in there - I was worried my mind wsa going - 16 is a little too young to be going senile as yet ;p
Well, I'm fairly certain it works (I've tested it), but it remains to be seen if it actually brings any benefit. Any testers? ;p
I have one other idea...but if it wouldn't work, it's somewhat absurd....
*wanders off muttering to himself*
Wrayal
Yes that routine actually returns the kernel to retail... It was included in my original dual-boot fonts.
I never used the closed retail xbe and the part is missing in the normal dual habibi xbe so I never saw that piece. I wonder how that could have worked though since you cannot load the hexed xboxdash with a retail kernel.
pls excuse my ignorance, but does patching\unpatching the kernel reset the system? because if not, wouldnt it be possible to incorporate unpatching the kernel into the retail xboxdash.xbe, so that:
ueee (settings_adoc.xip) xbe > fonts > dualboot.xbe > (tray closed) so hacked msdash that has been patched to look for 'xboxdashdata.185ead00' somewhere else (preferably E or F) loads > hacked ms dash automatically unpathes kernel now that its loaded.
of course, all of this would only work if unpatching can be done without resetting the xbox.
however if this does work, it will solve the problem of how to keep 'xboxdashdata.185ead00' during a dashupdate.xbe (because 'xboxdashdata.185ead00' wouldnt be on C:\, it would be on E:\ or F:\)
Krayzie: the dash need not be hexed - why do you think this was of no use before we (at our own respective times ;p) came across an xbe that loaded its fonts from another location?
yeah well that's probably why I never took a closer look at the closed retail.xbe.
scimitar: one obvbious problem leaps out - the number of different xboxdash.xbes there are out there ;p
well, although there are several different versions, you could patch them all to look in the same location for dash files.
I.E:
...............................................................................
before patching:
dash 5960 looks in: C:\xboxdashdata.********\
dash 4920 looks in: C:\xboxdashdata.########\
etc.
after patching:
dash 5960 looks in: E:\msdashfiles\
dash 4920 looks in: E:\msdashfiles\
................................................................................
of course,
it would be up to the user to move his 'xboxdashdata.whatever' folder to E:\ and do the rename.
U cant edit the M$ dash for this purpose, since it should be run like retail (no hack means only signed code)
The problem of not being able to do anything with files only occured to me once, when using xboxhdm to copy a savegame. I never thought about that only being an issue on the E drive and it sounds kinda strange.. E is partition 1, C partition 2 thats also strange IMHO since most BIOS's boot from C (how often have you made a PC boot from something other then the 1st phisical partition?)
I'ma fiddle with xboxhdm once i get the time but i cant code or anything so all i can do is test. I think i recall not being able to delete a FOLDER with linux written files either.
CODE
Formatting partitions..."
sleep 2
mkfs.fatx /dev/hda50
mkfs.fatx /dev/hda51
mkfs.fatx /dev/hda52
mkfs.fatx /dev/hda53
mkfs.fatx /dev/hda54
so you see there is nothing special on E:\ drive. I best guess is that.. there is also same bug with c and other drives. What people experienec that E drive freezes their xbox is that when xboxdash or any other games writes files to E:\ drive, it cannt write properly because the mkfs.fatx tool is not perfect. Now, for C:\ drive, when dashupdate deletes whatever files in C drive, it will be able to delete it but wont be able to write the files properly.
There is little hope of solving this bug since last update of mkfs.fatx in xbox-linux cvs was about 21 months ago..
I think if we put a blank xboxdashdata.1012a700 folder in C:\ root and then fill up C:\ drive then it will look for older dash. ( may be it looks first for oldest dash and then go up) and delete contents of it.. and then when it will try to create an xboxdashdata.185ead00 folder, then it wont because there no space to extract. ( is that thinking right..
)
kingroach: actually, the latest is for the 2.6 which is relatively recent, but just unworkably slow :\
I'm pretty sure my comment about EOF a couple of pages back was the reason for the read only problem - rmenhal stated pretty much exactly the saem thing elsewhere
Wrayal
as far as the read only xboxhdm linux "thing" goes...an easy way to test it would be to write a shadowc.img file to your C drive and have nkpatcher load it up. if you can't edit that C drive then the "bug" exists on the C drive too. it's possible that it never came up that it effects the C drive as well because the xbox never really writes anything to the C drive. it won't really make a difference though as it seems to only prevent altering the files, not completely deleting them...and that's what the dashupdate does.
as for the dualboot...wouldn't it have to unpatch before launching the xbe? i don't see how it could load msdash and THEN unpatch the key. if that's the case, if you had a game in the drive it would run fine...but otherwise wouldn't it just load xboxdash.xbe which would run the exploit? is it really possible to fully return it to stock and then run an xbe of your choice?! otherwise it seems a lot like coldbooting.
you rename original 5659.03 msdash to msdash.xbe or something like that. and put xboxdashdata.xx, fonts and audio folder in C:\
UEEE>loads fonts from "xodash" folder>loads signed "dualboot.xbe"
now dualboot works.
say if
tray open> dualboot.xbe>closed_retail.xbe ( unpatches "habibi" sig)>msdash.xbe (from C:\ root)
try closed>dualboot.xbe>nkpatcher.xbe/pbl.xbe>loads dash.xbe
lengthy boot chain but should work as "wrayal" stated but I got no live console to test it out.
QUOTE
as far as the read only xboxhdm linux "thing" goes...an easy way to test it would be to write a shadowc.img file to your C drive and have nkpatcher load it up. if you can't edit that C drive then the "bug" exists on the C drive too.
I created shadowc.img with xboxhdm long time ago and then copied msdash files there and it works. again pc based apps have no problem writing mkfs.fatx formatted drive.dont know about msdash. I will be testing this soon.
QUOTE(cmiz @ May 7 2005, 07:10 AM - 2nd aspect)
as for the dualboot...wouldn't it have to unpatch before launching the xbe? i don't see how it could load msdash and THEN unpatch the key. if that's the case, if you had a game in the drive it would run fine...but otherwise wouldn't it just load xboxdash.xbe which would run the exploit? is it really possible to fully return it to stock and then run an xbe of your choice?! otherwise it seems a lot like coldbooting.
Ndure's /C/xboxdash.xbe would be invoked via quick and/or full boots, so as long as the 'return to retail' doesn't cause either, the M$ dash would result. (The .xbe that's invoked after re-establishing the M$ public key is a renamed, M$ signed xboxdash.xbe.)
QUOTE(eh. @ May 4 2005, 07:19 PM)
For those interested, here's the beta test outline...
(Take full backups and ensure your box is currently chip, tsop, gamesave or swap recoverable ... just in case!)To implement Ndure, backup everything (as per the usual guidelines,
especially the C-partition!) and then do the following:
Confirm that you have a backup of UEEE's files plus your 185ead00
dashboard and former pre-live dashboard (i.e. 4817 or earlier).
If you don't have ALL of these available, then DO NOT PROCEED!!
(Until you have recovered the required components below.)
ftp into your Xbox (with full administrative rights) and ...
a. format the REAL C-partition (or delete all of its contents)
b. copy 185ead00's XOdash folder and all its contents to /C/XOdash
c. Copy UEEE's ernie.xtf to /C/XOdash/ernie.xtf
(this .xtf MUST be copied into place before the one that follows)
d. Copy UEEE's Xbox.xtf to /C/XOdash/Xbox.xtf
(use the one for your kernel version [or the generic one if you're
unsure] but it must be named Xbox.xtf)
e. copy UEEE's media folder and all its contents to /C/media
(which *optionally* includes zero, one or two "start up" .xmv files
[live.xmv | liveloop.xmv])
f. copy UEEE's xonlinedash.xbe to /C/xboxdash.xbe
(this is the C-partition's primary start up file and MUST be named
xboxdash.xbe)
g. copy pre-live dash's Xbox Book.xtf to /C/Xbox Book.xtf
(this provides retail disc support)
h. copy pre-live dash's Xbox.xtf to /C/Xbox.xtf
(this provides retail disc support)
i. create an empty directory named /C/fonts.du
(this serves as an important reminder reminder NOT to have a
"/C/fonts" directory!)
j. create an empty directory named /C/xboxdashdat.du
(this serves as an important reminder NOT to have a
"/C/xboxdashdatA.WHATEVER" directory!)
k. copy any files that YOU need in the C-partition to support the
E:/default.xbe (or equiv.) referenced by the UEEE fonts
l. make sure you have all files that YOU need in the other partitions
to support the E:/default.xbe (or equiv.) referenced by the UEEE fonts
m. create a huge file (ideally shadowc.img) that consumes all of the
remaining space on the C-partition, except for 1Mb!
(you can actually leave up to 1.2Mb free space on the C-partition,
BUT ANY MORE CAN BE A RISK!)
... re-start the Xbox (and enjoy Ndure)!
.
.
.
Ahead of a better method, re. the tray-state selectable {retail|softmod} dashupdate.xbe risk, here's a potential workaround...
require the msxboxdash.xbe to be version 185ead00 (and therefore the associated dashboard files too)
Ndure the C-partition, except remove (or purge) /C/fonts instead of performing steps a. and b.
backup the xboxdashdata.185ead00
.
.
.
when dashupdate.xbe runs it will:
i. successfully stage the xboxdashdata.whatever content into xboxdashdat.du
ii. fail to stage the fonts contents into fonts.du
.
.
.
boot up the softmod;
purge xboxdashdat.du and fonts.du
recover the xboxdashdata.185ead00 from the backup
_______
Footnote: "whatever" could be 17f14d00, 185a6100 or 185ead00.
QUOTE(kingroach @ May 7 2005, 04:12 PM)
I created shadowc.img with xboxhdm long time ago and then copied msdash files there and it works. again pc based apps have no problem writing mkfs.fatx formatted drive.dont know about msdash. I will be testing this soon.
Yeah u can write on a virtual C image place with xboxhdm, but u cant delete the shadowc.img file! (AFAIK, my TV broke down
so cant test anything)
Edit: Footnote addition...QUOTE(eh. @ May 7 2005, 10:08 PM)
Ahead of a better method, re. the tray-state selectable {retail|softmod} dashupdate.xbe risk, here's a potential workaround...require the msxboxdash.xbe to be version 185ead00 (and therefore the associated dashboard files too)
Ndure the C-partition, except remove (or purge) /C/fonts instead of performing steps a. and b.
backup the xboxdashdata.185ead00
.
.
.
when dashupdate.xbe runs it will:
i. successfully stage the xboxdashdata.whatever content into xboxdashdat.du
ii. fail to stage the fonts contents into fonts.du
.
.
.
boot up the softmod;
purge xboxdashdat.du and fonts.du
recover the xboxdashdata.185ead00 from the backup
_______
Footnote: "whatever" could be
17e4cd00, 17f14d00, 185a6100 or 185ead00.
I've successfully tested the above with Closed-Retail.xbe on my 3944. If anyone has done likewise with a 5838 yet, please confirm.
Btw, I was pleasantly surprised to find that my interpretation of the "Closed-Retail.xbe" name was incorrect ... the closed tray state activated the softmod (and open tray resulted in the retail 5960v185ead00).
QUOTE(eh. @ May 8 2005, 05:28 PM)
Edit: Footnote
addition...
I've successfully tested the above with Closed-Retail.xbe on my 3944. If anyone has done likewise with a 5838 yet, please confirm.Btw, I was pleasantly surprised to find that my interpretation of the "Closed-Retail.xbe" name was incorrect ... the closed tray state activated the softmod (and open tray resulted in the retail 5960v185ead00).
Yep, that confusion is mostly on my part. When I created the first tray state fonts I named them incorrectly. People seemed to understand and to avoid further confusion left them with their 'inappropriate' names.. heh
Hahey! It worked...but how much useful does it achieve? Non-coldboot live?
Wrayal
Hello I am wondering about the 16 maybe being a typo oh and if not whether that is human years. d;
QUOTE(wrayal @ May 6 2005, 05:53 PM)
Heh, took me a sec to see why you always paste things like that. Now I see. Well, thankfully that routine is in there - I was worried my mind wsa going - 16 is a little too young to be going senile as yet ;p
Well, I'm fairly certain it works (I've tested it), but it remains to be seen if it actually brings any benefit. Any testers? ;p
I have one other idea...but if it wouldn't work, it's somewhat absurd....
*wanders off muttering to himself*
Wrayal
...wondering about me being 16?? (yes - that is human years ;p)
hey, im 15, but then again....im not the smartest guy around when it comes to xboxes and stuff..
anyway, with the dual boot-unpatch thing, wouldnt it be possible to play retail game backups on live?
hear me out..
switch out the 'C:\msdash.xbe' with a HDD signed game xbe (I.E: Mechassault 1 is signed to run off the HDD AND xbox dvds) and rename the game xbe to msdash.xbe.
2 move the games folders and stuff to the root of C. (or wherever msdash.xbe is located.)
power off. power on woith tray closed. xboxdash>fonts>dualboot>(tray closed)>msdash.xbe[mechassault default.xbe]
QUOTE(scimitar116 @ May 10 2005, 05:16 PM)
hey, im 15, but then again....im not the smartest guy around when it comes to xboxes and stuff..
anyway, with the dual boot-unpatch thing, wouldnt it be possible to play retail game backups on live?
hear me out..
switch out the 'C:\msdash.xbe' with a HDD signed game xbe (I.E: Mechassault 1 is signed to run off the HDD AND xbox dvds) and rename the game xbe to msdash.xbe.
2 move the games folders and stuff to the root of C. (or wherever msdash.xbe is located.)
power off. power on woith tray closed. xboxdash>fonts>dualboot>(tray closed)>msdash.xbe[mechassault default.xbe]
that method is quite similar to the way people were playing backups on live before.
too bad the method was discovered by M$ and somehow they manage to check the gamexbe and at what point it is loaded so it will most likely not work and result in a ban.
ROFL, I see, it was a complement - it just confused me at first ;p.
Meh, I'm not the smartest guy by any stretch of the imagination either - was just lucky enough to receive a certain package, and have seen the function of closed_retail.
RE the MA thing - another hack that would have been VERY popular that stayed behind closed doors somewhat.
The only thing that occurs to me is the how to the the xonline.xbe. Normally, I'd say xbins would have qualms about it, but then they hosted UXE-complete. Still, a full set of patches would be useful for a potential replacement to mechInstaller for anyone who has the time ;p
Wrayal
Hello I am wondering if the dark side application of this would result in account termination oh and that is much more serious than a ban oh and I am also wondering whether the outlined light side method might be acceptable to XBox Linux implementors.
ok so say i have the closed-retail.xbe on my xbox. if i open the tray it is in retail mode so i can access the live dash rite??? also if i put a retail game in and close the tray will i be able to go on live like that. also how do it set up the closed-retail.xbe well actually just what does it boot when its open/closed. thx
QUOTE(mckenn88 @ May 12 2005, 02:33 AM)
ok so say i have the closed-retail.xbe on my xbox. if i open the tray it is in retail mode so i can access the live dash rite??
Not AFAIK! The MS Dashboard?, yes (so you can rip audio tracks, manage memory, etc) (but you could already do that anyway with a hex'ed MSDash, or a virtual 'C'!), but, no, not the xonlinedash.xbe - since it looks in the same locations for it's fonts as the FUSE/Ndure exploit.
IIRC FUSE/Ndure's benefits over UXE are:- Allows cold booted XBL retail games to download game updates from XBL (i.e. the exploit no longer get's in the way)! (I didn't realise that having UXE installed prevented this
) - Allows 'all three' (
) DVD-Videos with XBOX demos to play! - Allows 'both' (?) the multi-game DVD XBOX games to play!
I imagine the first point is very useful to XBL users. But given the wide interest in FUSE/Ndure, I fear I may be missing something. 
Im being slightly discourteous to eh and Ndure
technically it could be viewed as superior to UXE as it leaves the XBOX HDD in a nearer-to-pure-retail state, which probably has unforeseen compatibility benefits.
Pedros: does not the fact that you can boot to MS dash with retail kernel not allow you to run games on live without having to cold boot?
(also, there was the suggestion I posted a couple of pages back for running xonline.xbe on live, but I suspect that may be a little excessive....)
.·.: it ought to be useful for Linux. I produced a package a couple of months back based on precisely this setup, except that I could not distribute it due to the fact that it contained an MS xbe. With patches, sure, but....these patches don't exist as yet ;p
Wrayal
QUOTE(wrayal @ May 12 2005, 09:23 AM)
Pedros: does not the fact that you can boot to MS dash with retail kernel not allow you to run games on live without having to cold boot?
True, but how's that any advantage? Even with retail MS Dash running, you still have to get up out ya chair, eject the DVD-tray, pop the retail XBL game DVD in the DVD-tray, and close it (and then, yes, it only warm boots). It's not like you've got the convenience of selecting the XBL game from a menu and from the HDD or anything.
Since the MS Dashboard hasn't been hex'ed and the kernel is still retail, I guess you can take advantage of the boot Dashboard's XBL auto sign-on, and "buddy-online" chimes. (Assuming that's all built into the boot Dashboard! - never used XBL myself
).
Pedros: heh, I suppose - just a personal preference. The concept of needing a cold boot always seemed a little too hackish ;p
(as you probably know from your MI disassembly, Myria and co went to a lot of trouble to ensure a cold boot was not needed IIRC...)
Hello I am wondering if this new open+retail system setup is the answer for below oh and it has now been tested on a 5838 as well.
QUOTE(garyopa @ May 5 2005, 02:34 PM)
Looks nice. But this new version loads directly into Nkpatcher, or your
modded setup, is there anyone to disable it from booting directly to
bring you to a MS dash (unmodded) and then "trigger" it. I like UEEE
switching method, just wish it was faster (no keystokes).
Another pleasant surprise; changing dashboard settings, such as language (via the open tray retail state, with corresponding UEEE fonts) doesn't cause my 3944 to hang next boot.
Consequently, it seems Ndure might not suffer from the related memory layout issues that UXE has!
If anyone finds otherwise (especially with kernel specific fonts) please provide details...
I oughta write a guide for Ndure and put it on XGuides, assuming this stuff isn't alpha still.
(I never know what the fuck's going on, lol, I struggle to get into the development of things but just end up getting kicked around.)
Just looking for something new to do!
Thanks RiceCake, that would be awesome! It's far from alpha...
(i) rmenhal's readme.txt (below) was dated Oct.16/04 in the ueee.zip scene-release and its fonts seem to be more stable than UDE/2/UXE's; 
(ii) beta testing of Ndure deployments (mostly as per the previous page) has all but completed ... entirely successfully. 
CODE
DISCLAIMER:
-----------
Use at your own risk. It is very easy to make a mistake here. This guide is
very rudimentary and makes assumptions that a newbie may find puzzling.
Required:
---------
- An xonlinedash.xbe file from MS dashboard version 4920. There are two
supported versions:
* Dashboard 4920 (0x17CDC100, UXE dash)
- xonlinedash.xbe has file size 1929216.
- file md5sum: 8da4d816604e9b9d5aa69d1fd395a48e
- works with all kernels (3944-5838) and all regions.
* Dashboard 4920 (0x1012A700)
- xonlinedash.xbe has the same file size 1929216
- file md5sum: ffd55eb62f21d1f00585dbf9d02a1503
- works with kernels 3944-5530 and all regions.
- A set of stray support files in dash 4920 C:\xodash\media directory.
(You can remove the XMV animation files and a few others.)
- Your own default.xbe you wish to run after boot up. This may
be e.g. an executable for a replacement dashboard or a boot loader
(Linux boot loader, Phoenix BIOS Loader etc.) The file default.xbe
must be signed with the HABIBI-key (you can sign with the xbedump
program.)
The exploit itself depends on two additional files, Xbox.xtf and ernie.xtf.
The directory fonts/s1929216 contains Xbox.xtfs for both supported versions
(same fonts work since only the XBE header is different).
Ernie is the file fonts/ernie.xtf.
The required dash files are contained in the dashfiles directory.
Quick installation guide:
-------------------------
It is recommended that you first set language to English in the original dashboard's
settings menu (this is an UDE/UXE recommendation and may be unnecessary here.
Effects of such settings are currently unknown).
1. Rename your current C:\xboxdash.xbe to C:\orig-xboxdash.xbe
2. Copy dashfiles/xonlinedash.xbe to C:\xboxdash.xbe
3. Copy dashfiles/media directory and all files there to C:\media
4. Copy ernie.xtf to C:\xodash\ (IMPORTANT: do NOT change the order of steps 4
and 5.)
5. Select an Xbox.xtf file corresponding to your kernel version. E.g. if you have
kernel version 5101, select the file fonts/s1929216/Xbox-5101-01.xtf. Copy it to
C:\xodash\Xbox.xtf. Note that you MUST rename the file to Xbox.xtf.
If you can't find an Xbox.xtf file for your kernel version, use Xbox-generic.xtf.
6. Copy your own HABIBI-signed default.xbe to E:\default.xbe. This file
can be e.g. dashboard executable or Phoenix BIOS Loader executable.
7. Reboot. Your box should now run E:\default.xbe automatically.
If it doesn't, double check everything. DO NOT LEAVE YOUR XBOX FOR EXTENDED
PERIODS OF TIME IN A STATE WHERE IT CANNOT BOOT INTO A DASHBOARD. Especially
do not unplug the Xbox in such a state. If you do, your Xbox may not boot
even a DVD game disc (007/MechAssault/Splinter Cell) upon the next power up
and will then probably need to be opened to recover. So if things don't work
out, reverse step 1.
NOTE: do not change the order of steps 4 and 5. Ernie must appear first in the
actual directory data on the disk. This matters for both kernel-specific and
generic fonts.
If you have done everything ABSOLUTELY CERTAINLY CORRECT (triple checked,
and triple installed) so far, and it still doesn't work (freezes in the big X
logo and white MS text under it), you may have one of the rare Xboxes that
need additional steps:
8. Copy fonts/ts/s.xtf to C:\xodash\s.xtf
Still not working:
9. Copy the s.xtf also to C:\xodash\s2.xtf
Still not working:
10. Copy the s.xtf also to C:\xodash\s3.xtf
If you wish to change your language setting to something else than
English (in case you want an MS dashboard derivative such as thc lite),
beware that you may need to do steps 8-10 to make it work after the change.
Editing the default.xbe path and file name:
-------------------------------------------
If you wish to boot some other file than E:\default.xbe you may hex-edit
ernie.xtf. The path and file name string there has 12 zero bytes after it and
these may be freely replaced to make the string longer. You may also recompile
the file ernie.asm (source code in src directory).
-rmenhal
QUOTE(eh. @ May 14 2005, 06:47 PM)
Thanks RiceCake, that would be awesome! It's far from alpha...
(i) rmenhal's readme.txt (below) was dated Oct.16/04 in the ueee.zip scene-release and its fonts seem to be more stable than UDE/2/UXE's;

Yeah, this has exploit been known about for a while (days after UXE was released in fact), but we saw no purpose/audience for it in an already confusing exploit market space. However, eh found one!
This Ndure sounds real interesting..maybe the best benefits for it are yet to be discovered ..dual eeprom/msdash settings? virtual and real(open tray)..though i'm not sure if that could be any use myself
I look forward to reading your guide 'Ricecake', if you decide to make one as i'm slightly unsure of some of the lingo
edit (question).. the c:\virtualc.img (recomended) is to stop any updates..right?
It is used to stop XBox Live updates. Thats why it has to be such a perfect size.
Anyhow I'll start trying to build a guide for Ndure, incase anyone needs a good guide on installing it. Just gotta find a good program to make big empty files of specific sizes (Anyone know a good one?). I've only been using a hex editor to build my shadow C files and I don't really wanna explain how to do that!
I think TeamXecuter or someone had a nifty little program for building dummy files at one time, but I haven't been able to find it.
I can create empty file in linux.. and then probably .zip.rar it.. I never tried any windows program since its much easier in linux..
I could create a nice installer with xboxhdm but problem is the damn pre live fonts.. they are just too big to include in a package..
edit: here you go.. ( who says windows is dumb)..
in command type :
fsutil file createnew 1mbfile.img 1048576
this will create a blank file of 1MB in size..multiply by the number to get your desired dummy file.
Yeah the problem with making a generic one is that is the hack needs a specific size virtual C drive. Other people might have crap leftover on their C drive or something so there is no 'generic' size.
I've created a 256Mb virtual C file before and RAR'ed it. Hehe, goes from 256Mb to about 7Kb!
Anyhow what is this fsutils? Must be a Windows XP program, because I sure as hell haven't heard of it.
Edit: Eh, forget it! Found a neater alternative. Even has a UI!
http://xguides.xbox-...eCake/Dummy.exe
so in the future is there going to be some official release of Ndure or like an auto-installer of something. im not really for auto-installers but i was just wondering if this is going to be officially released to the public or if its only for "those who find it"
Read above, I'm planning to write a manual-install guide on XGuides soon.
hmmm could somebody post a lists of pro's and cons between the two cuz I'm still confused.
From what I gather it will stop xbox live updates but to my knowledge UXE does the same. Or should it be upcomming live updates that is gonna be stopped and still let you use live or something?
The stability part is interesting though but UXE is also pretty stable IMO
The dual boot part is also interesting but still no acces to the xonlinedash which kinda sucks.
I still have to decide if this is worthy enough to create some krayzie ndure installer.
QUOTE(RiceCake @ May 15 2005, 03:58 AM)
Anyhow what is this fsutils? Must be a Windows XP program, because I sure as hell haven't heard of it.
he means open command prompt (start>run> then type what he put.)
It's built into windows
@krayzie: some folks are already producing "their" Ndure installers!
yeah that's nice. I'm still uncertain over all it's benefits though.
QUOTE(Olipro @ May 15 2005, 10:35 PM)
hook me up with whatever you're smoking...
QUOTE(wrayal @ May 6 2005, 01:43 AM - most)
yeah, no live console I'd guess (it's ages since I've done any of this, but IIRC it remaps and does an absolute path). There is one option, albeit somewhat complex. Setup shadowC type system. Let live console boot, then remove all the patches (find a kernel call it doesnt make until after it has loaded fonts, and stick in a 'removal' hook there).

Alternatively (with the {Softmod|Retail} setup) just renaming four files would effectively toggle to retail boot state, facilitating Live console access on those (rare?) occasions when it's required.
It seems that the Ndure fonts are indeed more stable than UXE's, which could be quite significant for North American 1.6's (at least)!
Consequently, it may be of interest for others to test the following (simple/starter) install accordingly too. This provides the same ("minimal") level of functionality as UXE, but with less vulnerabilities...
1. copy UEEE's media folder and all its contents to /C/media
2. Copy UEEE's ernie.xtf to /C/xodash/ernie.xtf *AND* to /C/fonts/ernie.xtf
(this .xtf MUST be put in the xodash directory before the one that follows)
3. Copy UEEE's Xbox.xtf to /C/xodash/Xbox.xtf *AND* to /C/fonts/Xbox.xtf
(use the one for your kernel version [or the generic one if you're unsure] but it must be named Xbox.xtf)
4. copy UEEE's xonlinedash.xbe to /C/xboxdash.xbe
____
Take the usual backup/recovery precautions and ensure your /E/default.xbe (or equivalent) plus its support files are in place first!
I'll write a tutorial when I understand this Ndure stuff...
Complicated as hell...
And yeah I kinda wonder too what the real advantage is. Looks like it still fucks up XBox Live and stuff...
.. I liked the original plan better.. have the ability to boot msdash with closed-retail.xbe..
QUOTE(jonels @ May 19 2005, 12:17 AM)
my noobish guess would be that it a simpler way to stop xbox live updates when an original is booted ???
I dunno either where the thread with the UEEE package is and if the link is still working. Since the fonts and the patch are legal to distribute maybe someone could host them?
QUOTE(RiceCake @ May 18 2005, 03:47 PM)
I'll write a tutorial when I understand this Ndure stuff...
QUOTE(kingroach @ May 18 2005, 04:00 PM)
why do we need any fonts in C:\fonts?..

.. I liked the original plan better.. have the ability to boot msdash with closed-retail.xbe..

You can still do that kingroach (it's "stage 3" above) and was outlined on a previous page. 
QUOTE(jonels @ May 18 2005, 04:17 PM)
my noobish guess would be that it a simpler way to stop xbox live updates when an original is booted ???
Yeah, I'm up for hosting too. Again, PM.
Wrayal
Its been available with my installer.. Follow my sig..
Since I got webspace right here on XBox-Scene, I'd like to be able to host some files.
One of the reasons I made XGuides.
Stupid ass Base64 especially.
Anyhow thanks for the tips there eh, I figured it had something to do with anti-fuck-up-ness.
QUOTE(eh. @ May 19 2005, 07:07 AM)
No worries RiceCake; your offer of assistance was appreciated. Reducing the gap between hardmod features and softmods is complicated for sure.
I don't know if I should post this here but considering that all the great Soft mod minds are in here I guess I should do it anyway 
A small but very good suggestion to improve the soft mod in general is NOT to boot to a ''default.xbe'' it's really easy to install XBMC or something else on the E drive and overwrite the default.xbe.
It happen when someone copy's a game to the E drive and doesn't rename the Xbe. It happen when someone installs XBMC on the E drive accidentally.
It could happen if you place the ''new halo 2 maps'' installer in your E:\ Root''
It could happen in so many cases that this is worth considering.
Guys, can you PLEASE rename the booted Xbe in any later font release? Boot it to something like ''softmod.xbe'', ''Donotremove.xbe'' or ''important.xbe'' so that this doesn't happen.
I just finished doing a hotswap for someone who copyed the entire XBMC directly to the E:\ drive, ''I always do this when I install software, I dind't knew it worked different on the Xbox''.
Please, consider this
the name and path isnt a big thing.. u can just edit the fonts to change the .xbe name or path..
QUOTE(eh. @ May 19 2005, 07:25 AM)
Better safe than sorry that's for sure jonels.
is "settings_adoc.xip" the same as "xonlinedash.xbe" from 4920 ? can i rename that and use it for Ndure
I'll host this on XGuides assuming its the real file.
Edit: ANYONE releasing any softmod related files (that are legal!) please contact me here! I have webspace right here on XBox-Scene XGuides that is entirely devoted to helping organize tutorials and such!
ueee.zip download:
http://xguides.xbox-.../users/devz3ro/
Enjoy. Please don't link to that file from another site. You'll just get an error anyhow.
Many thanks for hosting it RiceCake.
Let's hope everyone trying it for Ndure performs the setup steps in this thread (and not those in the readme.txt or for UEEE)... 
QUOTE(krayzie @ May 19 2005, 12:33 PM)
Thanks for this outline.
(Chuckles) I'm lost again. 'Starter' kit, fonts, alot of references to UXE...
(Starts decyphering the entire post)
A few minutes later...
So, basically, your running some setup (yet to understand fully) that exploits the Xbox but leaves the normal fonts in place for coldbooting. By doing this, games that need the fonts work fine, but so do dashboard update XBE's and things. To thwart these from hosing the C drive, you need that massive shadow C file so the updater will dump out and not hose the softmod. Furthermore, to prevent Live or other programs from trying to force you to update your dashboard all the time, you have the Live data folder from the latest dashboard there to trick any programs into thinking you have the latest dashboard version.
I think thats right. Please tell me if I am!
If I'm not, well, go to hell
...
Goes back to scrutinizing every tiny tidbit of ASM to create the perfect UDE2 install for himself...
I'm starting to understand this code. Its too bad I dunno what the fuck all these byte writes and move really do, because I wish I could help program something for the 'Scene.
QUOTE(RiceCake @ May 19 2005, 09:53 PM - part)
So, basically, your running some setup (yet to understand fully) that exploits the Xbox but leaves the normal fonts in place for coldbooting. By doing this, games that need the fonts work fine, but so do dashboard update XBE's and things. To thwart these from hosing the C drive, you need that massive shadow C file so the updater will dump out and not hose the softmod. Furthermore, to prevent Live or other programs from trying to force you to update your dashboard all the time, you have the Live data folder from the latest dashboard there to trick any programs into thinking you have the latest dashboard version.

So your starter kit has the UXE fonts still installed (corrupting update.xbe's and such) just for sort of a preliminary thing to make sure it works right?
Whats this dual boot install process? Are you talking about using the Closed-Retail.xbe to launch the MS Dashboard?
Edit: Hm, I think I finally see. The online dashboard is being used to exploit the Xbox with different fonts to prevent corrupting the fonts that programs and updaters use.
So why do you need a pre-Live dashboards fonts? Just out of curiosity.
Wouldn't these have compatibility problems with games designed for 5960 dashboards?
Roughly:
/c/xboxdash.xbe (UEEE exploited XBE)
/c/xodash/*.xtf crashes, overflows, exploits.
/c/media/* support files.
/c/*.xtf Provided to support games.
/c/*.* Space-wasting file to crash updaters.
hmmm okay...well since UXE prevents any dashupgrades also, the only real benefit of ndure would be the coldbooting of the discs that require the fonts.
XBox Live for people too lazy to use an uninstall/reinstall script.
Well, it works, hehe.
Hey does this XBE set ROJ?
I should throw together a little UDD package...
QUOTE(RiceCake @ May 19 2005, 10:27 PM)
So your starter kit has the UXE fonts still installed (corrupting update.xbe's and such) just for sort of a preliminary thing to make sure it works right?
QUOTE(krayzie @ May 19 2005, 10:53 PM)
hmmm okay...well since UXE prevents any dashupgrades also, the only real benefit of ndure would be the coldbooting of the discs that require the fonts.

WRONG; Ndure provides that plus more stable fonts plus update.xbe support too.
.
Nice job with the pre-Live fonts though. Didn't know there was any checksumming going on there. I'll have to check out those other links...
Wait...there more stable than what? The whole line of Uberdash hacks?
If so I am so pissed. I wasted so much time making a UDE2 install thinking it was the most stable..
hmmm okay but in conjunction with a virtual eeprom UXE is just as stable and offers more "genericness" right?
And what good does bring us having a working update.xbe but failing update?
I think he means the fonts are more reliable, further reducing the possibility of the XBox overflowing all over the place and possibly crashing at bootup.
Update.xbe support, heh...other than being stable and coldboot Live supported, sounds like no other real advantages.
I thought he mean the stability issue with memory layout changes due to parentall or language settings.
coldbooting to live is done for ages so that's not new. I only still wonder what advantage the working update.xbe brings us.
QUOTE(krayzie @ May 19 2005, 11:11 PM)
hmmm okay but in conjunction with a virtual eeprom UXE is just as stable and offers more "genericness" right?
well I noticed making the ueee installer that the generic fonts did not one time work on different versions. the kernel specific worked allright though. that's why I had to make a kernel selection option.
Anyway so update.xbe is used for game updates and changes things in the tdata/udata area. hmmm Didn't know that (still don't use live). thanks
Hm, looks like I'll be using Ndure to mod my Xbox!
After I crack it up into a doubledash hack of course...
QUOTE(RiceCake @ May 19 2005, 11:09 PM - part)
Wait...there more stable than what? The whole line of Uberdash hacks?
QUOTE(krayzie @ May 19 2005, 11:27 PM - part)
well I noticed making the ueee installer that the generic fonts did not one time work on different versions. the kernel specific worked allright though. that's why I had to make a kernel selection option.


Edit: Hey nobody mentioned yet, does this XBE set ROJ?
Interested in setting up an ejectable-doubledash on my XBox, or UDD.
Never got it off the ground before.
)
It doesn't set ROJ ... it's from the Uber4920 Dashboard - exploiters' heaven! (UD-eh!
)
does the xonlinedash.xbe have to be the correct one for the kernel ?
in the ueee.zip readme.txt it states there to be 2 versions one of which .....
"file md5sum: ffd55eb62f21d1f00585dbf9d02a1503" ....
only supports kernels 3944-5530
having a 5838 myself would i need to make sure i have the other version which supports 3944-5838 ... i have obtained a copy of 4920 and the xonlinedash.xbe seems to be the wrong one for my system
can anybody clarify this for me ?
if you put your 5659 dash.. the patcher will produce the ud-eh xonlinedah.xbe . which is 1929216 byte size and works with all kernels.. The other xonlinedash.xbe is normal 4920 dash's .xbe which only works upto 5530 kernel..Look at triggernums page.. that site has complete uee package..
oh and make sure you have a recent fully recoverable backup of your XBOX before installing Ndure. 
http://forums.xbox-s...dpost&p=2623155
So if we perform the "Closed-Retail.xbe" Part of Ndure, what will happen is this?:
(Looking at it from a what's on TV Standpoint)
-I turn the Xbox on with the Power Button. And the Modded Xbox State Appears. I cannot go on Xbox Live
-I turn the Xbox on with the Eject Button, And after the MSDashboard (5960 v-185ead00) Appears I can access the Xbox Live Dash part of the Dashboard, and I can place a Retail bought Game into that OPEN DVD-ROM Drive, close it, and I can play that game Perfectly on Xbox Live, and Access the Live console if needed.
If this is true Ndure here I come.
@jonels: phew - well done!
@LafferUSA:
Re. Power Button, that's right (provided the softmod has Live blocking enabled).
Re. Eject Button, there's still no direct Live dash|console access (that's toggled, per
) but a new benefit for some will be that game discs can be changed without coldboots between them.
QUOTE(Olipro @ May 21 2005, 01:35 PM)
I "upgraded" to Ndure, not quite sure why it was necessary since UXE has worked flawlessly on my PAL 1.6 for a while now, but I got moderately bored.
@kingroach: what does it do and for what benefit/s?
Hehe, yeah thats the dualboot XBE's on my site, for anyone who poked around in the devz3ro folder.
http://xguides.xbox-.../users/devz3ro/
Its just the files I got outta the Base64 file recompressed into a RAR so its easier to get. Although when I compiled my dualboot XBE I had to copy the header.asm file from NKPatcher over, else it would give alot of weird .text errors when running NASM.
By the way you can grab NASM off of http://nasm.sourceforge.net, get the lastest 32 bit DOS binaries.
Hey by the way - anyone ever played with the ASM code in these dualboot XBE's? I noticed there was some LED code in there, but I didn't want it and just commented it out.
If this breaks stuff please lemme know before I chuck it on my XBox later.
Edit: Dual retail? Why not just leave the MS dash installed!
QUOTE(RiceCake @ May 21 2005, 10:56 AM - 1st bit)
Hehe, yeah thats the dualboot XBE's on my site, for anyone who poked around in the devz3ro folder.

If you get a chance, please try it with the ueee.zip's generic Xbox.xtf too ... plus see if changing any (real)eeprom dashboard settings stop it booting.
_______
Warning: with any softmod, changing the parental control settings might result in gamesave exploit discs not booting.
QUOTE(eh. @ May 21 2005, 06:48 PM)
@kingroach: what does it do and for what benefit/s?
i will try some settings/generic.xtf later as the kids are using it all day... i must say that loading seems quicker in games, could be my imagination
ok.. I am having some strange situation..I did setup ndure+ude2 in my xbox like this:
bert_ate_earnie.xtf+scraps.xtf in C:\fonts
UDE2 xboxdash.xbe in C:\
Ndure xboxdash.xbe ( renamed xboxdash2.xbe) in C:\
Ndure media+xodash folder
xboxdashdata.185ead00 folder in C:\
and in my E:\ drive root:
PBL lite+x2.4981 ( named default2.xbe)
Nkpatcher (named default.xbe)
now in default.. UDE2 boots, and it boots Nkpatcher. I can launch ndure ( xboxdash2.xbe) from C:\ drive and its set upped to boot PBL lite and it boots PBL fine ( I can understand its PBL from the little different video output)..
so I guess both working fine..
now I have 5659 dash's xboxdash.xbe renamed mxboadash.xbe..in C:\ root..
When I boot into UDE2, the LED is orange from dashboard, WHen I launch Ndure from dashboard, the LED remains orange and it launch PBL.. but when I launch mxboxdash.xbe.. the LED turns Grren and I can hear HD spinning and then it launchs Nkpatcher (!!).. I was expecting a error 21 since the fonts are not in C:\fonts..
It seems like pre live fonts in C:\ root with UDE2 fonts C:\fonts.. make 5659 dash exploitable?.. wtf is this.. or am I mising something.. and mxboadsh.xbe is total retails..no hexed..
@kingroach: are you indicating you've changed /C/xodash/ernie.xft to reference /E/default2.xbe?
If so, maybe the "5659 dash's xboxdash.xbe renamed mxboadash.xbe..in C:\ root" is an issue ... 5960 rev. 185EAD00's xboxdash.xbe accesses /C/xboxdashdata.185ead00 (the 5659 xboxdash.xbe's don't).
___
Btw, 5960 rev. 185EAD00's xboxdash.xbe requires 5960 rev. 185EAD00's xonlinedash.xbe to be in /C/xodash too.
CODE
xboxdash.xbe (the settings_adoc.xip)
xodash\ernie.xtf
xodash\xbox.xtf
media\Xbg\ (xodash\media\Xbg)
media\content\ (xodash\media\content)
nkpatcher\default.xbe
I left out the \media\content\ age, country, creditcards, states and valuelength folders since they are only called upon when using the signup option in the XBL dash (so i figured)
Tested with a generic ernie.xtf on a 1.1 PAL 4817
Setup without an installer around it is only 3,01 MB (instead of the 65,1 MB i started with)
Uhh...do without virtual EEPROM?
Where the hell did that come from.
Keep using the virtual EEPROM because if you don't, your giving up a security that could easily save your ass in several situations.
Edit: Nice job though. Clean little install.
Since the fonts are more stable, they will load even if there are changes to the true eeprom.. UXE prefers a standard USA eeprom config otherwise it hangs.. I agree there is no need to drop the feature just because it will boot without it though..
I said CAN do without didn't I?
But hey i got a chip + softmod so i would like te be able to change my eeprom settings properly.
@Cio: thanks for determining and sharing ways to reduce the baseline requirement!
1.214.284 bytes, with english only its 772.337 bytes
Total setup now 3.161.310 bytes
Total setup english only 2.719.363 bytes
QUOTE(RiceCake @ Jun 6 2005, 03:56 PM - part)
One of the reasons to use a specific kernel font I guess.
QUOTE(caxtor @ Jun 6 2005, 10:33 PM)
Need some help, im stuck here. Here's my setup:
QUOTE(eh. @ Jun 7 2005, 10:24 AM)
Is all of the original content in the C:\xboxdashdata.185EAD00 folder (and is it 185EAD00's original content that's also in C:\xodash)?
@caxtor: well done!
(Btw, if you haven't filled up C yet then this linked proggie could assist.)
QUOTE(.·. @ Jun 10 2005, 03:52 AM)
Hello I am wondering if this can ever be a problem with wildcards oh and that is because of the actual order of processing

oh and if it can then the script could first do the copy everything command oh and then delete the font files followed by copying them again but individually in sequence.
Ok some questions:
)
@caxtor: although you don't actually need to fill up C, it is definitely advisable (so that the box will automatically still be able to boot the softmod even if dashupdate.xbe ever runs).
It's quite unlikely that dashupdate.xbe will run, during normal usage of the box, but it's possible for it to!
If it does and you manually prevent it getting too far (which seems to be before half way on its progress bar for the Ndure "retail" setup) your box can still boot the tray-closed softmod.
If you fill up C you don't need to manually intervene ... it will stop automatically when it runs out of C-partition space. 
_______
Note: the key to this, for the "retail" setup, is that M$'s C:\fonts\*.xtf files are NOT installed!
Re. "Can I acces Live from the MS dashboard like retail?"...
Yes you can (except for the Live tab's options and the Network settings) via the tray-open boot state, because that leaves the retail kernel in memory.
Re. "A live account must be setup before the ndure install or it can be after?"...
As with all softmods, it is advisable to do that before. However, with the Ndure "retail" setup it can be after by enabling the Live tab's options (and Network settings) - per this
arrowed post's correction.
So what will happen if I accidentaly went into the LIVE's tab in the tray-open boot state?
Will it mess up with Ndure even with C filled up?
QUOTE(caxtor @ Jun 10 2005, 03:22 PM)
So what will happen if I accidentaly went into the LIVE's tab in the tray-open boot state?
)
@caxtor: nothing negative like that would happen at all...
If you go into the LIVE tab in the tray-open boot state, its options will appear as normal.
If you've done the toggle then its options will work properly (because the retail kernel is in memory).
If you haven't done the toggle then its options will just hang (or maybe FRAG like UXE would, I forget which) without doing anything.
QUOTE(eh. @ Jun 10 2005, 03:48 PM)
(@DaddyJ: your reply indicates a misinterpretation.

)
Cleared it up...... Thanks///
Ummm, time to make this an official thread?
And add it to these?
http://forums.xbox-s...howtopic=243341
QUOTE(eh. @ Jun 10 2005, 02:48 PM)
(@DaddyJ: your reply indicates a misinterpretation.

)
I just tried it again on my NTSC 3944 (which has 725 KB free on C) and it worked fine...
The Live tab's new account or account recovery options (plus the Settings -> Network Settings) result in the green spinning circle being displayed, then the screen goes blank and stays that way (because it hangs due to /C/xboxdash.xbe not being the one it mandates).
@caxtor: are you certain you have all of the original 185ead00 dash's /C/xodash/ content in place (per
)?
Running my highly modified Ndure install with specific kernel fonts for my 4817, works perfectly!
My excuse for wasting space on C though was to simply copy all my music files over until it started to fail. 0 bytes free space, hehe.

@anyone with an Ndure "retail" setup: please post if you experience the reboot too. (You can test it via Settings -> Network Settings if you don't want to use the Live tab's options.)
@caxtor: I've tried to cause my box to act differently (such as by renaming the non-font files in /C/xodash/) but have been unable to cause a reboot. Please could you try renaming /C/xodash/xonlinedash.xbe to another name (I added a character to the extension) and post what happens when you then do a tray-open boot...
It used to be Bert before Ernie. That was why they called it that, so the B would copy before the E.
there is no bert.. only earnie.xtf and Xbox.xtf.. actually the name doesnt matter either..
QUOTE(eh. @ Jun 12 2005, 02:44 PM)
@anyone with an Ndure "retail" setup: please post if you experience the reboot too. (You can test it via Settings -> Network Settings if you don't want to use the Live tab's options.)
OK, so i renamed xonlinedash.xbe and from open-tray boot i get error 21, but closed still works.
Any other ideas?
Yes, if you have a separate (backup) copy of the xonlinedash.xbe...
() leave that renamed file (was /C/xodash/xonlinedash.xbe) exactly as it now is
(i) delete /C/xodashdata.185ead00/settings_adoc.xip
(ii) copy the backup of xonlinedash.xbe into /C/xodash/
(iii) open-tray boot (it should work again)
(iv) Settings -> Network Settings ... do you get the spinning green circle?
Same results as before, i get the spinning circle for 1 or 2 secs, freeze and then reboots.
(
Hmm, me thinks this is potentially indicative of another exploit opportunity!
)
@caxtor: you only mentioned the reboot before; re. the "freeze" which of these is it?
a. the circle stops spinning (but stays on the screen)
b. the screen goes blank (no circle anymore)
c. something else (please describe)
Also, roughly how long is it between the freeze and the reboot?
(
AFK...
)
I'm losing my job soon so didn't have the time to help out alot, but i did have some time to e-mail iriez and PM devz3ro, still no reply or whatever so i doubt the Ndure basic files will be hosted by xbins anytime soon.
However, there are other (un)usual places where you might find em.
This is however, again 2 late, since a "new" exploit opertunity has already been found so it seems.
OK, the circle appears, it starts to rotate for about 1 or 2 secs, then it freezes for 1 sec then the screen goes black for another sec (the time it takes for fonts exploit to run again and the closed-retail.xbe to chek tray-state and run the corresponding xbe) and then MS Dashboard appears again (or unleashx, depending on my tray state).
@caxtor: if the tray is open (when you choose the Live related option) does it stay open while all of this happens, or does it close during the reboot (and you then manually re-open it to get the M$ dash again)?
(Also, what kernel version is your box and are you using the specific or generic Ndure font?)
QUOTE(eh. @ Jun 13 2005, 12:26 PM)
@caxtor: if the tray is open (when you choose the Live related option) does it stay open while all of this happens, or does it close during the reboot (and you then manually re-open it to get the M$ dash again)?
Im kernel 5101 and im using specific font.
That's amazing ... your box seems to be double dashing via 185ead00 (which I believe is "a first")! 
If you wanted to investigate that further, you could rename Ndure's /C/xboxdash.xbe to be /C/xboxdash.xbeN then rename the retail /C/msxboxdash.xbe to be /C/xboxdash.xbe. Booting would then be to the M$ dash (irrespective of tray state) and choosing a Live option with the tray closed would trigger the softmod (if it's double dashing)...
It doesnet work...
I get error 21...
It seams it will load the Live dash, but after a few secs screen flickers and bam: error 21
I believe there are no exploited fonts to load during the whole process...
Im out for some hours l8r...
Hmm ... tray-closed shouldn't 21 for the Live options with this test scenario, as everything it needs was left in place.
Did you maybe have the tray open (which would almost certainly 21 with this temporary setup)?
I noticed something different, when i go to a Live button, i get the circle spinning for 2 secs then it freezes for 1 sec, and then it moves about 3 pixels down and right (And it looks kinda different to me) then it spins for another 2 secs and then 21.
Could it be that the file settings_adoc.xip is not present (you told me to delet it some posts ago)?
(
/me thinks maybe your box is possessed! 
)
The settings_adoc.xip is only necessary for the EEE, sfaik. I deleted it to gain its disc space and before you ask, that aspect's unrelated too.
(Btw, you didn't confirm whether your feedback was all/part re. the closed-tray test scenario.)
(
AFK for many hours (including pondering...)
)
O yes, i tried it with both tray closed ansd opened... same result = 21.
QUOTE(eh. @ Jun 11 2005, 10:33 AM)
I just tried it again on my NTSC 3944 (which has 725 KB free on C) and it worked fine...
QUOTE(eh. @ Jun 13 2005, 04:42 PM)
@Cio: it's not too late ... Ndure
is the "new" direct booting opportunity (which is the
primary type of exploit). [/i]).
@Cio: although your disappointment is understandable I think that's unfair!
Iriez didn't make the judgement, devz3ro did (and IMO it's understandable too) and they have done and still do loads for the community, time permitting. Plus don't forget that devz3ro kindly produced and scene-released the ueee.zip, that Ndure evolved from.
___
Footnote: I suspect that if a package with enhanced XBL capabilities is produced, devz3ro would consider that as something new and progress it further (if it's X-S legit of course)...
Dont worry eh., I love to test new stuff with my box
. i had my box besides a PC and just hotswapped cus I lost my 007 
Going back to my first problem, my Live related buutons cause reboot... Which files should I check to ensure that I have the correct ones present?
I currently have:
/C/xodash/ with the 185ead00 original files and fonts inside...
Are those all the ones I should check?
Hello I am wondering if you have tried renaming the 3 files to activate the live options oh and that really does work
oh and also the splinter cell eastereggsploit can be used for renaming them back eh
oh and thank you everyone involved for the . . B E S T . . S O F T M O D . . E V E R . .

What your box does isn't a problem ... I wish mine did that instead of hanging (which isn't a problem either but it's less convenient)!*
Based on what you've posted, I'm sure you have everything setup correctly. If you want the additional testing changes can be reverted, but only the EEE would be affected if you don't.
_
* On your box the Live options are successfully re-running Ndure's "XBL dashboard" (the initially booted .xbe) via persisted memory, whereas on mine they are not.
QUOTE(.·. @ Jun 14 2005, 11:25 PM)
Hello I am wondering if you have tried renaming the 3 files to activate the live options oh and that really does work

oh and also the splinter cell eastereggsploit can be used for renaming them back eh

oh and thank you everyone involved for the . . B E S T . . S O F T M O D . . E V E R . .

Thanks and I'm aware of the EEE possibilites (and also that implementing them safely needs additional knowledge/understanding)!
I'm wondering if Kingroach is still working on the NDURE file setup. That and NDURE basic files (with proper names etc) for download would be really nice.
.. I was quite busy playing GTA:SA..I am addicted to the damn game.. The setup is done.. I will do few tweaks.. I would release it.. but I am having trouble writing ftp apps for it.. but does an ftp app required?..
..

Edit: Yeah SA is nice, although i dont really like the music (hip hop is nice but damn.. isn't shooting people in-game offense enough?)
More edit: Could you get it to create xiso output? (and then use an ava gamesave/qwix)
QUOTE(eh. @ Jun 13 2005, 09:42 AM)
@Cio: it's not too late ... Ndure is the "new" direct booting opportunity (which is the primary type of exploit).
I'm kinda of confused by this. direct booting to what?
thanks
the xonlinedash (then called settings_adoc.xip) and exploitable fonts are also used in EEE, only there they are triggered with "finger magic".
With Ndure, the xonlindash is renamed to xboxdash.xbe and booted directly, like any other "normal" font exploit (UDE/UXE style bootstrap).
I am just drunk enough right now to actually post how entertaining it can be to watch an intelligent human being talk to himself...
*edit* oh IN TEXT!
LMAO
And do be a flaming pirate kiddy
It bad fer ya health argg!
oh and almost all of my posts were to add value or moderate oh but since I *am* the weakest link . . G O O D B Y E . .
Dude.. relax.. stay off dope and alcohol (at least for a while), spend some time with your g/f (or b/f) and last but not least, stop crapping the thread.
And it was indeed supposed to be "don't" not "do".
BTW GTA: SA is getting boring
.
Hehe, thought this was a good laugh. Pretty relevant to these forums...
QUOTE
How many forum members does it takes to change a light bulb?
1 to change the light bulb and to post that the light bulb has been changed
14 to share similar experiences of changing light bulbs and how the light bulb could have been changed differently
7 to caution about the dangers of changing light bulbs
1 to move it to the Lighting section
2 to argue then move it to the Electricals section
7 to point out spelling/grammar errors in posts about changing light bulbs
5 to flame the spell checkers
3 to correct spelling/grammar flames
6 to argue over whether it's "lightbulb" or "light bulb" ... another 6 to condemn those 6 as stupid
2 industry professionals to inform the group that the proper term is "lamp"
15 know-it-alls who claim they were in the industry, and that "light bulb" is perfectly correct
19 to post that this forum is not about light bulbs and to please take this discussion to a lightbulb forum
11 to defend the posting to this forum saying that we all use light bulbs and therefore the posts are relevant to this forum
36 to debate which method of changing light bulbs is superior, where to buy the best light bulbs, what brand of light bulbs work best for this technique and what brands are faulty
7 to post URL's where one can see examples of different light bulbs
4 to post that the URL's were posted incorrectly and then post the corrected URL's
3 to post about links they found from the URL's that are relevant to this group which makes light bulbs relevant to this group
13 to link all posts to date, quote them in their entirety including all headers and signatures, and add "Me too"
5 to post to the group that they will no longer post because they cannot handle the light bulb controversy
4 to say "didn't we go through this already a short time ago?"
13 to say "do a Google search on light bulbs before posting questions about light bulbs"
1 forum lurker to respond to the original post 6 months from now and start it all over again.
) ... does anyone know whether either of these was most likely coincidental (or not)?
(i)
Further to this arrowed post
, one box proved to need the kernel specific file with scrap files for Ndure to boot!
Interestingly, that box plus one other I know of had font peculiarities with UEEE too, and both boxes have split TSOP mods.
(ii)
Another oddity was encountered booting Ndure on a different box ... the screen blanked after the boot's big X and M$ was displayed (and it stayed blank)!
Interestingly, the fonts being used at the time included a UEEE auto-installer's modified ernie.xtf that wasn't 433 bytes (which rmenhal's is in the ueee.zip). Using that 433 byte version and hexing it instead (so the Habibi file path;name was as per the package's) seemed to remedy it.
QUOTE(eh. @ Jun 19 2005, 08:29 AM)
"Talking to" potential concerns (but more appropriately this time!

) ... does anyone know whether either of these was
most likely coincidental (or not)?
Here's an Ndure "retail" setup enhancement (re. Live console usage):
a. create a zero length file named /C/xodash/Xbox.xtf0
b. create a directory named /C/xodash/fonts0
c. put the post-live Xbox Book.xtf and Xbox.xtf into /C/xodash/fonts0/
To enable Live console usage, script/do these five file renames:
/C/xboxdash.xbe --> /C/xboxdash.xbeN
/C/msxboxdash.xbe --> /C/xboxdash.xbe
/C/xodash/Xbox.xtf --> /C/xodash/Xbox.xtfN
/C/xodash/Xbox.xtf0 --> /C/xodash/Xbox.xtf
/C/xodash/fonts0 --> /C/xodash/fonts
(To toggle back, via gamesave exploit, script/do the renames in reverse ["bottom up"] sequence.)
@kingroach: the enhancement specifically causes the "Live console" (/C/xodash/xonlinedash.xbe) to use the "Live fonts". Can the extra setup ('a.', 'b.', & 'c.' above) be easily added to your Ndure Installer's "Patching C drive files" feature?
) xonlinedash.xbe; UXE boots its update.xbe.
Ndure can also be used as an easter egg exploit (UEEE); UXE cannot.
Ndure doesn't suffer from "memory layout issues" when booting; UXE does.
Ndure can be configured in various setups (it's extensible); UXE can be configured one way (it's limited).
Each Ndure setup provides new features; UXE provides almost all of Ndure's minimal features.
Ndure's "starter" and "basic" setups support all language settings; UXE doesn't.
Ndure's "basic" setup hangs when retail fonts are accessed; UXE FRAGS.
Ndure "fonts" and "retail" setups additionally allow .xbe's to run that use retail fonts; UXE doesn't.
Ndure "fonts" and "retail" setups allow XBL game updates to run; UXE doesn't.
Ndure's "retail" setup additionally allows open-tray boot to an XBL compliant retail state*; UXE doesn't.
Ndure's "retail" setup quickly toggles between Live console access and back; UXE doesn't.
___
* Although unlikely to happen in normal use, this unique Ndure "retail" feature is partially impacted by Live 2.0+ dash updates though. It's quickly and easily recovered if that ever happens (as the softmod still boots) but ideally someone will eventually figure out a way to prevent it happening...
QUOTE
Ndure "fonts" and "retail" setups additionally allow .xbe's to run that use retail fonts; UXE doesn't.
NKpatcher solves this but on coldboots still doesn't help (no XBL support)
QUOTE
Although unlikely to happen in normal use, this unique Ndure "retail" feature is partially impacted by Live 2.0+ dash updates though. It's quickly and easily recovered if that ever happens (as the softmod still boots) but ideally someone will eventually figure out a way to prevent it happening...
Updates are prevented by filling up the C drive right? no probs there
QUOTE
Ndure's "retail" setup quickly toggles between Live console access and back; UXE doesn't.
Can you explain that a bit more. I was under the impression that switching files back and forth were exactly the same using Ndure or UXE. (switching from modded to retail might be quick but from retail to modded still requires the gamesave or easter egg.)
@ Cio. Isn't it something that even though everything is filled up it still changes some of the files on C:\. I thought I read that somewhere.
The switching is "faster" because renaming files would be enuff. Indeed, the same hassle applies to getting unsigned code to run again.
But EEE fonts are already in place, so basicly with a few more renames/copy operations, this could toggle between a UEEE and Ndure retail setup without needing anything from another drive for example.
You're right bout the update, but emtpty xboxdashadat.du and font.du folders prevent this (but where left out in the retail setup since they can create alot of confusion). I almost forgot about that.
QUOTE(Cio @ Jul 2 2005, 04:44 PM)
The switching is "faster" because renaming files would be enuff. Indeed, the same hassle applies to getting unsigned code to run again.
Well you dont need file off another drive etc, thus making the process faster. Apart from that, UXE doesn't nativly offer the function (Ndure does since it really is just EEE but bootstrapped)
But the way Eh formulated is wrong, they both allow it. Ndure is just a better candidate for Live! given the one exploit "does it all", and it never loses update.xbe support.
No offense BTW, but instead of holding on to UXE, you could just modify/rebuild you installer to install a Ndure/EEE setup with switcher
QUOTE
NKpatcher solves this but on coldboots still doesn't help (no XBL support)
Hmm, sure it can be worked around with the lesser font exploits, in the modded state, via hexed files or by having (i) nkpatcher (ii) an active ShadowC (iii) the retail fonts copied into the active ShadowC.
However, Ndure "solves it" (as do EEE and even audio exploits) but UXE doesn't and nor does nkpatcher ... "out of the box"!
QUOTE
Updates are prevented by filling up the C drive right? no probs there
Hmm, as posted numerous times, updates still run but are prevented from clobbering the softmod. With the "fonts" setup, no user followup is needed but with the "retail" setup some is (to re-establish the retail boot, as posted).
QUOTE
Can you explain that a bit more. I was under the impression that switching files back and forth were exactly the same using Ndure or UXE. (switching from modded to retail might be quick but from retail to modded still requires the gamesave or easter egg.)
Hmm, switching from modded to retail is faster plus easier and switching back is faster ... also since Ndure just has to rename files it doesn't have the level of disk corruption risk that UXE's workaround does!
QUOTE
The switching is "faster" because renaming files would be enuff. Indeed, the same hassle applies to getting unsigned code to run again.
Hmm, sure there are some "constants" in the process but it's the "variables" that differ.
QUOTE
But EEE fonts are already in place, so basicly with a few more renames/copy operations, this could toggle between a UEEE and Ndure retail setup without needing anything from another drive for example.
Hmm, it has nothing to do with UEEE and that won't be involved (as the Live console wouldn't be available if it was).
QUOTE
You're right bout the update, but emtpty xboxdashadat.du and font.du folders prevent this (but where left out in the retail setup since they can create alot of confusion). I almost forgot about that.
Hmm, he was close (for a change) and no they don't prevent it.
QUOTE
yeah I understand you need to rename stuff. I just wanted to know how this is different/faster then an UXE setup.
Hmm, then write out all of the steps involved and compare it with Ndure's fewer, quicker, easier ones ... you could see what's really quite obvious, if you weren't so narrow-minded!
QUOTE
Well you dont need file off another drive etc, thus making the process faster. Apart from that, UXE doesn't nativly offer the function (Ndure does since it really is just EEE but bootstrapped)
Hmm, actually the 'ure' (uber rmenhal exploit) bootstrap preceded its EEE usage (as UEEE) by some months, but the forum mods didn't release it ... why was that krayzie?
QUOTE
But the way Eh formulated is wrong, they both allow it. Ndure is just a better candidate for Live! given the one exploit "does it all", and it never loses update.xbe support.
Hmm, I didn't think so but I maybe didn't explain it clearly. Btw, I'm curious, is there anything that UXE is a better candidate for?
QUOTE
No offense BTW, but instead of holding on to UXE, you could just modify/rebuild you installer to install a Ndure/EEE setup with switcher
Hmm, I doubt that he could!
krayzie
Hmmmz
uxe needs to rename xboxdash.xbe and fonts to switch and ndure needs that too. If things were going faster it would be milliseconds. But yeah that's just the brain of some narrow minded n00b talking offcourse.
And yeah I'm offcourse way too stupid to set up some ndure installer. Like it would be some great deal... I never said I was going to stick with UXE btw. I just critisize the ndure sometimes since I feel it's a bit too romantisized compared to UXE sometimes. I agree it's better but it's not a whole lot better.
QUOTE
Hmm, as posted numerous times, updates still run but are prevented from clobbering the softmod. With the "fonts" setup, no user followup is needed but with the "retail" setup some is (to re-establish the retail boot, as posted).
The retail setup didn't interest me at the time, so for me just filling up the drive was enuff. I used a stripped down version with fonts at the time. guess ill go out and provide my only XBL using client with a restore disk.
QUOTE
Hmm, it has nothing to do with UEEE and that won't be involved (as the Live console wouldn't be available if it was).
Same fonts/exploitable xbe. IIRC there is an EEE variant that allowes full XBL console access. This means that with some renames an EE exploited dash with full XBL console access can be switched on/off with the Ndure retail setup, for those rare moments its needed.
QUOTE
Hmm, he was close (for a change) and no they don't prevent it.
Same as the first post. Thx for politely pointing this out so i can look into it.
QUOTE
Hmm, I didn't think so but I maybe didn't explain it clearly. Btw, I'm curious, is there anything that UXE is a better candidate for?
I feel the term "allow" is misused. It doesn't "prevent" it either. I think maybe "its a hassle to get XBE's that need the retail fonts working" would be less subjective.
NKpatcher is not something special, given the installers that have a shadowc and virtual eeprom enabled by default. Most UXE issues can be adress by this. HOWEVER this is NOT a solution for XBL or coldbooting stuff.
+ for Ndure from my perpective:
Coldboot support for ALL GAMES/DVD's
XBL download support
No need for a virtual eeprom (personal motivation -> chip+softmod setup)
Support for DVD remote + controller without any hassle (ofcourse you could use avalaunch bit the DVD player is still a bit buggy)
Seriously, im staying the fuck away from this flaming from now on. Anyone will agree that being able to place retail fonts on ur HD is seriously "revolutionairy". What the fuck is the point in debating small issues when you're making progress. This isn't the god damn UN security council forum.
So relax, have a beer, fiddle around with some stuff, test some things, build some installers, whatever. Just stop debating about jack shit and/or who has a bigger dick. Again, this isn't the UN security council forum. They can handle that.
Thanx. Yeah Sometimes things are not clear for me and then I tend to ask for some explanation. But somehow an understandable non-encrypted answer to a fairly simple question is hard to find and I have to read through stuff I didn't even bring up. I'm sure I could have found the answer myself if I had much time on my hands and read through the numerous posts in which only like 10 of them make sense. Anyway I apologize for askin all this stuff and stick to my own side of the forums from now on.
TO eh!:
Is there anyway to modify the "memory" location of ernie to make the
hack overflow work if you allow the NDURE bootscrap to play a .XMV
file at the beginning. I find the NDURE boots up fine if the two .XMV
files "live" and "liveloop" are deleted, but if they are left in place, the
XBOX just sits a BLACK screen after playing the two files (with the
complete) CONTENT directory, or looping the first file with the bare-bones
CONTENT directory.
What do you think of finding out the max. length of .XMV file which could
play without changing the "memory" location of ernie, or stopping the
hack overflow from working?
-----
Reason is, I want to put a small MODDED splashscreen in place before
anything boots up. I think that would be neat little trick or (feature).
@Cio: I think your's was (almost all) a great response. 
&
& Apologies to both of you re. my immature 'rant' post!
&
@krayzie: I don't think of you as "a noob" per se ... IMO you're like a cockatoo in comparison to other parrots. Also, I don't doubt you could do it technically; it's that you've opposed it so much and seem too "stuck in your ways" to change! 
@Anusko: I believe the kernel has passed control back to xboxdash.xbe (to display the invalid media message). With Ndure "retail" that'd re-activate nkpatcher (since the tray's closed), however, I suspect nkpatcher wasn't designed to expect a "pass-through" such as that.
@garyopa: I anticipate that's very possible and think it'd be cool (but I've neither the skills nor the desire to pursue it myself).
Perhaps it would be wize to leave this topic open for questions like garyopa has, and open up a new one with relationship to live compatibility's, with a definition of the fonts and retail setup + troubleshooters etc
That would clear up the need-to-know stuff factors from this almost insanly long and uncoherently ranting thread.
Corrections:
I always like hearing people mention XGuides
I might open up a page on XGuides about NDure concerning Live compatibility when I understand some of it. I haven't been keeping up with this thread (because, as always, your information is kinda widely scattered amongst other things!).
Keep up the good work.
I have an idea in the back of my mind, in getting the full LIVE console working with NDURE with no renaming of files, but I need to find some "unusual" place
for the complete "dashboard" package of all the files used by NDURE and UXE.
I know the UEEE.ZIP patcher changes the XODASH of 5920 into the special dash, but what about the "17CD100" files? In there a patcher for those?
QUOTE(garyopa @ Jul 6 2005, 04:27 PM)
I have an idea in the back of my mind, in getting the full LIVE console working with NDURE with no renaming of files
How r u gonna do that given the fact that there are exploited fonts in c:\xodash\
Not to be sceptical but, it's kinda impossible.. so please share your thoughts.
edit: does it relate to the xmv files?
Been playing with the LIVE console part.
There is no way to get the LIVE 2.0 console working, as
it needs to match up with the correct XBOXDASH.xbe
file on the "root" of your C:, and or course that file is
never write.
The part I been playing with is hacking the "17CDC100"
since it runs on all "kernal" versions. A parital LIVE
console, at least for the NEW account, recovery, and
NETWORK setup, all which normally DON'T work when
the system has been "soft-modded" with Ndure or UXE,
or even UEEE.
This features if working, I think would be the most
needed functions for a better "soft-hack" system.
I been working on the back of my mind, a way to
get this working, but I need more the the original
"17CDC100" dash files, and I can't seem to trick
XBOX live into giving them to me.
The UEEE patch, only makes the XODASH part,
including the "xonlinedash", and with the UXE
patcher, the "update" file is made, but there
does not seem to be source for the main
"xboxdash" file or the matching XIPS inside
the "17CDC100" directory.
Part of the trick is the fact, the the xonlinedash
looks both at "xodash" for the fonts and also
"xodash\fonts" for the fonts.
I also noticed, hacking thru the files, that all
versions of XBOX dash's, and all the XBE's
look also for a "THIRD" font called:
"GothicM.xtf" <--------- What happen to this font,
and would would happen with the system if the
XBE found this file instead.
Also I noticed in the 17CDC100 xonlinedash,
the following paths:
xbox-feb03\private\online\xodash\xodashmain\scenavigator.cpp
xbox-feb03\private\online\xodash\xodashlib\text.cpp
xbox-feb03\private\online\xodash\xodashlib\font.cpp
xbox-feb03\private\online\xodash\xodashlib\audiopump.cpp
Is this left over from the making the XBE, is it really a bunch
of smaller files merged together, like the XIP in the dash folder?
Just my random thoughts going into the wind of the scene, maybe
it will lead somewhere great...................................
A better way to implement Ndure "retail"! 
I thought of this a few days ago, but only just had opportunity to test it (so don't think "Why didn't eh tell us that before?", maybe think "How come no one else thought of or posted that?").
[HISTORY]
The Oct.2004 "uber rmenhal exploit" ('ure') didn't have automated dashupdate.xbe prevention - that's the "Next dimension" aspect (of 'Ndure'). Achieving it needs the pre-live /C/*.xtf instead of /C/fonts/*.xtf files.
However, Ndure "retail" evolved after that and it doesn't have automated dashupdate.xbe prevention. Along the same lines as the other Ndure setups, a "workaround" provides automated dashupdate.xbe protection of the softmod (but the xboxdashdata.185ead00 directory and contents have to be recovered to fix the open-tray "retail" mode).
That workaround has remained in place plus a subsequent workaround identified, for "fully compliant" Live console access (via /C/xodash/fonts) but I've now determined that neither of those are required for an Ndure'd "retail" setup...
[/HISTORY]
The Ndure "retail" setup can use (and only needs) the post-live /C/fonts/*.xtf's!
Here are the steps ... it LOOKS like LOTS more BUT it's mostly things that have previously been conveyed (essentially it's an Ndure'd retail 185ead00, without settings_adoc.xip, that doesn't have pre-live fonts):
A. starting with only M$'s 5960 release 185ead00 in the C-partition (for XBL usage, a "properly" updated box is best!)
B. delete settings_adoc.xip (from its xboxdashdata.185ead00 folder)
C. copy 185ead00's xodash folder (and contents) to a temporary PC folder
D. perform the ueee.zip(c/o XGuides)'s ueee.exe on the temporary PC folder
E. obtain the ueee.zip's ernie.xtf then Xbox.xtf (kernel specific or generic if you prefer)
F. hex the ernie.xtf to reference the filepath;filename.xbe you want the initial, habibi signed file to be
G. if you want, hex/rename then habibi sign the "Closed-Retail.xbe"(c/o XGuides) to reference the (closed-tray) softmod startup filepath/filename that you want
H. ftp your version of the "Closed-Retail.xbe" file (from step G) to be the initial, habibi signed file (per step F)
I. ftp your (closed-tray) softmod startup file into place (per step G) along with any support files it requires
J. ftp the ernie.xtf (step E) first then your Xbox.xtf (step F) into the C-partition's xodash folder
K. rename xboxdash.xbe to be msxboxdash.xbe in the root of C
L. ftp the xboxdash.xbe and Media folder+content from temporary PC folder (step D) into the root of C
M. ftp whatever else you want into the C-partition (except in the xboxdashdata.185ead00 folder!)
N. fill up the rest of the C-partition leaving less than 4 Mb free!
O. Backup the xboxdashdata.185ead00 folder+contents(without settings_adoc.xip in it)! ... If ever dashupdate.xbe runs then, via the (closed-tray) softmod, delete the fonts.du and xboxdashdat.du folder+contents then recover the xboxdashdata.185ead00 folder+contents(without settings_adoc.xip in it) from the backup.
_______
Therefore, the toggle for Live console access is just 3 file renames again, as per this arrowed post
(and note the warning therein 'kiddies').
@kingroach: consequently the pre-live .xtf's will no longer be required in your Ndure installer, plus it won't need those xodash .xtf0&fonts0 enhancements!
(OT)@garyopa: good luck with your research; I hope you got the X-S routed email I sent a day or two ago ... plus I expect this little puzzle
(arrowed post) and its "secret" linked post will be everything you need for 17cdc100...
Edit:
3...
so, here is the setup:
C:\Audio
C:\fonts ( with retail fonts)
C:\media (ueee)
C:\xboxdashdata.185ead00 (without settings_adoc.xip)
C:\xodash ( ernie.xtf+Xbox.xtf)
C:\xboxdash.xbe ( xonlinedash.xbe)
C:\msxboxdash.xbe
C:\junk+junk+junk
C:\needed files
+
softmod activate/deactivate:(via unleashx)
C:\xboxdash.xbe >< C:\xboxdash.xbeN
C:\msxboxdash.xbe >< C:\xboxdash.xbe
C:\xodash/Xbox.xtf >< C:\xodash/Xbox.xtfN
+
Gamesave backup
Can you boot games like topspin/ncaa with this setup? also, can you not have any settings_adoc.xip, or can you replace it with something such as the sceee settings_adoc.xip xbe and still be fine.
[CONFESSION]
When I began formulating Ndure ("FUSE" back then) I made an extremely dumb mistake during initial testing! Unfortunately, that subsequently resulted in me stating the requirement for pre-live fonts (for the Ndure "fonts" setup).
Within the past week I've re-tested as much as I can, using the post-live fonts. Everything has worked correctly and those fonts are definitely recommended instead...
Consequently, when implementing the Ndure "retail" OR THE "fonts" setup ... only the M$ C/fonts/*.xtf are necessary.
[/CONFESSION]
@garyopa(re. link): deleting the settings_adoc.xip AND leaving less than 4 MB free in the C-partition causes dashupdate.xbe to automatically fail (which consequently prevents the [closed-tray] softmod being clobbered).
@dumdasme: SFAIK, all discs requiring M$ .xtf's to coldboot will work with the Ndure "fonts" and "retail" setups. Re. the SCEEE:
(i) if it's implemented then, SFAIA, dashupdate.xbe will NOT automatically fail and it would subsequently clobber the (closed-tray) softmod, if it's not manually interrupted in time!
(ii) an alternative, "new" method (outlined long ago in this thread) is much more desirable now ... as Ndure's automated protection is unaffected by it (plus it doesn't suffer from ROE/J)!! 
@everyone: if you don't have 4920 Version 17CDC100 (UD-eh!) and would like to try it, clicking the arrow at the bottom of my previous post and applying the technique 'described' therein (which includes a linked patch file) effectively produces it. 
___
1...
So, those of you with UD-eh!, via either of my previous posts or elsewhere, can "go back in time" and do all (SFAIK) dash 4920-specific exploits on boxes with any current kernel version. 
Moreover, its xboxdash.xbe can also be used another way ... and that remaining mystery is now easy to solve (given my X-S-wide clue)! 
Thereafter, hopefully someone with suitable ability will facilitate it (maybe using this linked post's .asm as a guideline
) for the benefit of XBL users when the Live console's enabled...
_
0
QUOTE(garyopa @ Jul 7 2005, 09:45 PM)
...
QUOTE(eh. @ Jul 16 2005, 11:33 PM)
So, those of you with UD-eh!, via either of my previous posts or elsewhere, can "go back in time" and do
all (SFAIK) dash 4920-specific exploits on boxes with
any current kernel version.

edit.. i wonder who else is going around by a different name on this forum ...rhemhal ?? -> ...eh???
My bad; I should have announced it first. I admire that you were "defending kingroach" from what could have been a "noob attack"...
(Re. rmenhal - I WISH!)
"UXE coldboots everything"
No it doesn't, retail fonts are missing, so any xbe's that require them (demo/dual game disks) wont coldboot! Sometimes they frag, sometimes they activate the hack and boot after nkpatcher runs
"Virtual eeprom is not needed"
Mempory layout issue anyone? I suggest using a virtual eeprom, or like me, you'll figure out changing your video settings isn't a very smart move when using UXE.
"DVD remote works perfectly fine"
Yes sure it does, but my point was a fast way (simple reboot) to either play DVD's with the remote or the controller, no need to change settings EVER, anyone can watch DVD's with this setup, however they want
"Im probably going to upgrade to Ndure because it has some safety-nets, and is not so easy to destroy as UXE is (little kids playing on the xbox)"
NKpatcher offers the security. Ndure does not, nor does UXE. If you're not using a virtual eeprom then ndure can compensate security that your setup lacks. As mine did (via chip/softmod setup).
In reading this I got the idea that Virtual eeprom was not needed with Ndure to insure stability. But both Krayize and Kingroach have it as part of their installers.
So does Virtual eeprom add anything to the functioning of Ndure? Do I need it?
QUOTE(L0stX @ Aug 15 2005, 06:46 AM)
In reading this I got the idea that Virtual eeprom was not needed with Ndure to insure stability. But both Krayize and Kingroach have it as part of their installers.
UDDEE? SCEEE?
God damn. Why do you guys always need to post this stuff in only one thread scattering it amongst 20-30 different posts! Lol.
RiceCake, your post originally had me thinking you might be on to UDDEE+SCEEE re. Ndure...
That EEE combo's the other reason for the 21 MB filler in kingroach's installer v2.1; although I haven't tried it myself (as the 21 MB DDEEE's all I need) I'm sure it would work.
{: Personally I refer to UDDEE+SCEEE as "Upita" and think anyone that uses it deserves sore thumbs! :}
I've now verified the above using the underground SCEEE files, along with six XIP* files from SlaYer's v2.5 and its patched XBE* as settings_adoc.xip in xboxdashdata.185ead00 (*re. steps i & ii here: http://forums.xbox-s...post&p=2351577).
Just the 21 MB filler needed deleting, but slightly more space was consumed (leaving ~335 KB free in the Ndure 2.1's real-C).
{: It worked perfectly, but took me more than a minute of button-mashing to launch the exploited dash! :}
kingroach, those needed for the minimal/optimal amount of space usage indicated here: http://forums.xbox-s...dpost&p=2893298
(It's easier to understand and/or prove the 'Uber Double Dash' by getting it working in "full" in the virtual-C first.)
Btw, the Ndure 2.1 real-C layout re. UDDEE and UDDAE is...
Audio/
bios/
Fonts/
media/
shadowc/
xboxdashdata.17cdc100/
xboxdashdata.185ead00/
xodash/
msxboxdash.xbe
xboxdash.xbe
1. is all of the 35.7MB needed?.. what files can be left out?
2. Where does the DD fonts goes?
QUOTE(kingroach @ Sep 8 2005, 10:04 PM)
1. is all of the 35.7MB needed?.. what files can be left out?
Update re.QUOTE(eh. @ Jul 16 2005, 11:33 PM)
So, those of you with UD-eh!, via either of my previous posts or elsewhere, can "go back in time" and do
all (SFAIK) dash 4920-specific exploits on boxes with
any current kernel version.
Update re.
QUOTE(Ndure protagonist @ Oct 23 2005, 09:06 PM)
Update re.
QUOTE(krayzie @ Oct 23 2005, 09:30 PM)
I'm personally leaning more to a dual retail hacked dashboard (like a fuckmsed evox or xbmc) which should be possible now with Angerwounds just revealed secret app. This eliminates the need of the retail dashboard and therefore the dependacy of certain versions or update problems.
QUOTE(kingroach @ Oct 23 2005, 11:18 PM)
I heard you will be releasing package with xbmc.. its would be good since no need of retail msdash before going to live but does a retail evox/xbmc play games/apps from hd?.. I never tried funckms'd dashboard so dont know.
I think using a "retail" setup with anythingthing else completly shatteres the advantages to Ndure retail. Sure it's still "non-coldboot" XBL, but you dont have a friends list etc.
The *.du folder issue (error 21 on tray open boot) can be avoided by enabling auto-sign in. Also, without the retail dash setup, switching to a full retail state (with UDDAE backdoor) is not so easily done.
When using a hacked dash for non-coldboot XBL over the M$dash i see the following:
Pro:
No more error 21 due to dashupdates with auto sign in disabled
Future updates cause less hassle (if any)
Con:
No more M$ XBL fuctions such as friends list via menu.
Full retail state switching is harder (requires a backup on E)
But since i'm not assuming any smart moves from M$ that cant be overcome if a few weeks, and most live users have auto sign in enabled anyway, the only way i see this being really usefull for casual users, is if M$ overhauls XBL next month and the dash cant be used via the current open-tray setup (hash checking xboxdash.xbe for example, killing ANY softmod with XBL
).
Not that i oppose the goals BTW, just noting some points here. And i also thought fuckMS only applied to retail XBE's (cant be used on debug XBE's).
QUOTE(Cio @ Oct 24 2005, 12:21 PM)
Con:
The Ndure 'retail' setup alternative (that dashupdate.xbe's currently don't impact) is as follows:
the msxboxdash.xbe is the Uberdash's xboxdash.xbe;
its support directory is consequently xboxdashdata.17cdc100;
the current XBL compliant dash is installed with its xboxdash.xbe and xboxdashdata.{version*} renamed;
the MS dash xbe's and the renamed xboxdashdata directory are toggled via the Ndure (de)activation.
(Edit: the xboxdashdata.17cdc100 doesn't need to be renamed, as dashupdate.xbe's currently don't touch it.)
*If supported, such as by 185EAD00, the settings_adoc.xip could also be 17cdc100's xboxdash.xbe re. UDDAE (and the music directory or ST.DB would also be toggled)...
nice. again smart thinking
QUOTE(krayzie @ Oct 24 2005, 04:45 PM)
Excuse my lack of knowledge on the XBL situation but I though All XBL functions aren't working anyway with the dual retail setup. (don't they require xonlinedash.xbe?)
With more research, if we can get msxboxdash.xbe ( 5960+) to look in xboxdashdata.17cdc100 dircetory.. and FuckMS sign it..may be then dahupdate wont bother retail dash that much..
Aren't XBE's that connect to live hash checked now?!? Or does that only apply to games?
QUOTE(Cio @ Oct 24 2005, 09:47 PM)
Aren't XBE's that connect to live hash checked now?!? Or does that only apply to games?
QUOTE(krayzie @ Oct 24 2005, 08:04 PM)
that is the big question....
yeah that offcourse seems the most logical solution. but ms being ms you never know...
I bet they know by now.. I am sure they read the forums but I dont think they would care so much since we are not playing backups anymore.. and if xonlinedash.xbe is retail then it wouldnt be a problem.. When game actually launches then I doubt any more xboxdash trace remains in ram..
QUOTE(kingroach @ Oct 25 2005, 05:00 AM)
I bet they know by now.. I am sure they read the forums but I dont think they would care so much since we are not playing backups anymore.. and if xonlinedash.xbe is retail then it wouldnt be a problem.. When game actually launches then I doubt any more xboxdash trace remains in ram..
I thing the biggest problem we have is getting someone to risk blacklisting his CC and getting his account revoked, to test this.
I assume when connecting to live in any way, the kernel and running XBE are checked, but both only in RAM. Like Anusko said, why make seperate rules for the dashboard?
Anyone up to some testing is able to contact me anytime via AIM 'ANGERWOUND'.. Can help with the details of things as well as provide a bit of tech support on the app.
QUOTE(Anusko @ Oct 25 2005, 02:41 PM)
I can give 3 eeproms for free. Live isnt commercially available where I live (Portugal) so less than 1% xbox owners use it.
I just tried a fuckmssed (non-edited) xonlinedash.xbe and it connected to live fine. BUT since I don't use live and don't have an acount I only made it to the part in where you have to fill in your subscription code. I offcourse don't know when they do this checks (pre subscription or after signup) or when they ban the eeprom (right away or after hours/days/weeks) so I don't really know the value of this test......
I couldnt find how to edit the x.be to look in another folder.. The 5960 dash version number is 185ead00 so I changed .xbe version to 185ead01 and also rename xboxdashdata dircetory but it gives me error 21..
I've now edited xonlinedash to look for C:\xb0xdash.xbe instead of xboxdash.xbe and now loads fine out of my UXE setup. Connection established. Now if only wants to test with a real XBL acount...
QUOTE(krayzie @ Oct 25 2005, 11:43 PM)
I've now edited xonlinedash to look for C:\xb
0xdash.xbe instead of xboxdash.xbe and now loads fine out of my UXE setup. Connection established. Now if only wants to test with a real XBL acount...
ok.. I have done some tests with modified xboxdash.xbe and xonlinedash.xbe.. the results were quite good.
xonlinedash.xbe > look for xnoxdash.xbe
look for fonts in first C:\fonts, then C:\fonts\ then C:\
xboxdash.xbe > look for files in xnoxdashdata.185ead00
normally xnoxdash.xbe boots fine, with modified xonlinedash.xbe it goes to live console fine. But with xnoxdash.xbe and retail xonlinedash.xbe, xonlinedash.xbe reboots.
I put ndure fonts in C:\xodash\. modified xonlinedash.xbe goes to live console but unmodified xonlinedash.xbe loads nkpatcher. ( under modded state 5960 xonlinedash works with fonts)..
QUOTE(Cio @ Oct 24 2005, 02:29 PM)
I didn't know that either.. i once turned on with ndure retail while having a memory card with XBL account on it connected.
QUOTE(krayzie @ Oct 25 2005, 11:43 PM)
I've now edited xonlinedash to look for C:\xb
0xdash.xbe instead of xboxdash.xbe and now loads fine out of my UXE setup. Connection established. Now if only wants to test with a real XBL acount...
QUOTE(Ndure protagonist @ Oct 26 2005, 05:09 PM)
Wouldn't using a UXE setup revert to getting FRAG's (error 21) for discs that the need retail fonts and for XBL game updates?
on a second thought.. how are you supposed to launch a fuckms'd .xbe.. when you boot with eject button xbox goes back to retail.. from there you cannt launch a habibi signed .xbe.. if you just boot xonlinedash.xbe then thats different..
QUOTE(kingroach @ Oct 26 2005, 06:22 PM)
if you just boot xonlinedash.xbe then thats different..
If this works, your original ID about UXE with live console access will provide with a much faster way to create/manage XBL accounts than UDDAE.
Cio; I don't understand all of that, but you sure "sound" convincing! :}
How did you do the successful xonlinedash.xbe deletion test though? 185ead00's msxboxdash.xbe FRAG's for me when that's the case.
(Btw: the XBL network settings can be changed via the softmod boot, so the retail boot isn't required for that).
I renamend the 5960 xboxdash.xbe and placed it in xodash as xonlinedash.xbe.
It simply wants an XBE it can boot, it doesn't care what. This also works as bugfix for the hangs, the dash is simply reloaded is any functions from the xonlinedash.xbe are adressed.
But as kingroch posted, it might be better to use 4920's xboxdash.xbe for this, creating a DDAE that boots a hacked/fuckms'ed live console.
I know about netwqork settings, it's the least relevant issue IMHO, but worth mentioning.
{: So the xonlinedash.xbe was replaced, not just deleted then. :}
Regarding which, have you or anyone else considered the following? (I don't think it's already been discussed, here or in the fuckms thread, but am not certain...)
Note: This wouldn't have XBL account maintenance and troubleshooting (but I personally don't mind toggling to get those and UDDAEing back):
the msxboxdash.xbe is the 17CDC100 xboxdash.xbe (UberDash);
its support directory is consequently xboxdashdata.17cdc100;
the 185EAD00 dash is installed with its xboxdash.xbe and xonlinedash.xbe renamed;
its support directory is consequently xboxdashdata.185ead00*;
the 185EAD00 dash's xboxdash.xbe is also installed as the xonlinedash.xbe;
the retail boot (Uber)dash's Live tab launches the other (XBL)dash for Auto Sign-On etc.;
the XBL dash's Live tab (and network Settings) just cause it to re-launch;
the XBE's are toggled via the Ndure (de)activation**;
dashupdate.xbe would clobber the xboxdashdata.185ead00 but the retail boot would still work.
*the settings_adoc.xip would be 17CDC100's xboxdash.xbe for EEE usage
**the music directory or ST.DB could be toggled during the Ndure (de)activation re. UDDAE too
but wont having ndure fonts in xodash folder and different version xboxdash.xbe in C:\ will cause xonlinedash.xbe to reboot?..I assumed you will need a hacked xonlinedash to avoid clash with fonts in C:\xodash and changing xboxdash.xbe check to msxboxdash.xbe/xnoxdash.xbe check..and if thats hacked then you will need some form of exploit to run it and therefore UDDAE..
I am going to look for splinter cell game todat in gamestop.. if I find one I will test these.. however my preferable setup is:
xondash.xbe (fuckms'd)
xnoxdashdata.185ead00 ( safe from update)
C:\xodash\xonlinedash.xbe ( xboxdash.xbe , 4920)
C:\xodash\x2onlinedash.xbe (fuckms'd)
or
xondash.xbe (fuckms'd)
xnoxdashdata.185ead00 ( safe from update)
C:\xodash\xonlinedash.xbe ( xboxdash.xbe , 5960)
C:\xodash\x2onlinedash.xbe (fuckms'd)
C:\xnoxdashdata.185ead00\settings_adoc.xip ( xboxdash, 4920)
either way dircet UDDAE or indirect UDDAE will allows x2onlinedash.xbe to boot. If xnoxdash.xbe checks for C:\xodash\xonlinedash.xbe certificate then indircet UDDAe is the only way.
kingroach, I don't understand what you mean; I tested what I posted (except for the toggling bits, which I'm sure will work) and it behaved as described...
QUOTE(Ndure protagonist @ Oct 27 2005, 04:11 PM)
{: So the xonlinedash.xbe was replaced, not just deleted then. :}
QUOTE(Cio @ Oct 27 2005, 10:57 AM)
If you enable auto sign in, it keeps working even when the dashupdate has run. For some reason, you can still vieuw the xbl welcome screen (and insert a retail game) when only the *.du folders exist!
Didn't you also find that's only the case when there's zero free space on C (absolutely no bytes) at the time dashupdate runs though?
With the method I described above (that definitely works and doesn't have any such pre-requisites) the retail and softmod boots both continue to work after dashupdate has run...
I "discovered" that setup without FTP, so AFAIK it also works if you have less then 1 MB free. I'll test it some more then.
I would agree, changing the xboxdashdata folder name is a great solution for dashupdates, but it causes an extra obstacle for running the live console.
The check preformed on xb0xdash.xbe/xnoxdash.xbe would fail, meaning we cant just change paths but will need to remove the check altogether. I know i cant so thats why i didn't want to edit the 5960 xboxdash.xbe after realizing the possibility of live console access via post by you and krayzie.
yesterday, I was playing OXM November demo disk . When I launched XBL arcade demo, it updated xboxdash but what interesting is that it deleted xboxdashdata.17cdc100 folder in C:\..
kingroach, did the dash update fail?
Also, what does `xbedump dashupdate.xbe -dc` display for it?
oh last time C drive wasnt full..
Ndure retail setup+ xboxdash 5960 +xboxdashdata.17cdc100 folder( 86KB left). When I launch XBL Arcade, dashupdate launch it creates fonts.du, xboxdashdat.du and then update fails.. Ndure installation is intact.
I copied xboxdashdata.185ead00 folder and I chnaged msxboxdash.xbe to xbxodash.xbe and XBL arcade didnt ask fro update, then I copied ndure xboxdash.xbe in C:\ and changed xboxdash.xbe to msxboxdash.xbe and then XBL tried to update.. seems like having ndure xboxdash.xbe triggers update.
the xbedump -dc doesnt show anything special.. just shows game region CAN/USA and version 185ead00 and certificate 0x1ec
Yep, if dashupdate.xbe runs to completion its tidy-up phase includes deletion of the xboxdashdata.17cdc100 directory.
However, with an Ndure setup {: correctly implemented, ahem :} it doesn't get that far, at least for all the dashupdate.xbe's I've tested so far.
Yep, dashupdate.xbe's check the certificate version of both the xonlinedash.xbe and the xboxdash.xbe ... if either is less than its own then it runs.
Btw, what certificate date does that November OXM dashupdate.xbe have and what's its byte size?
QUOTE
Btw, what certificate date does that November OXM dashupdate.xbe have and what's its byte size?
QUOTE
=================================
XBE HEADER
=================================
MAGIC : XBEH
SIGNATURE : -
Base Address : 00010000
Header Size : 8192
XBE Size : 58395008
XBE Header Size : 388
Timestamp : 40A3EFC7
Cert.Offset : 00010184
CODE
Size of certificate : 0x000001EC
Certificate timestamp : 0x433C1E39 Thu Sep 29 11:02:49 2005
Title ID : 0x54540093
Title name : "Xbox Dashboard Updater"
Alternate title ID's :
none
Allowed media types : 0x00000202
: XBE_MEDIA_XBOX_DVD
Allowed game regions : 0x00000007
: XBE_REGION_US_CANADA
: XBE_REGION_JAPAN
: XBE_REGION_ELSEWHERE
Allowed game rating : 0x00000003
Disk number : 0x00000000
Version : 0x185EAD00
(It's external size is 58,421,248 bytes.)
Hence, the retail boot and softmod boot both survive current dashupdate.xbe's, for both of these new setup options:
http://forums.xbox-s...dpost&p=3000790
http://forums.xbox-s...dpost&p=3006012