Print

[eh.]

Corrections:

[RiceCake]

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.

[garyopa]

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?

[Cio]

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?

[garyopa]

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...................................

[eh.]

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...

[kingroach]

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

 

[dumdasme]

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.

[eh.]

[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...

[eh.]

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

[atomiX]

QUOTE(garyopa @ Jul 7 2005, 09:45 PM)

...

[Ndure protagonist]

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.

[jonels]

edit.. i wonder who else is going around by a different name on this forum ...rhemhal ?? -> ...eh???

[Ndure protagonist]

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!)

[Cio]

"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).