Print

[krayzie]

hmmm guess you never noticed the tutorials topic between the pinned ones. Anyway here's the link: http://forums.xbox-s...54#entry1651702

[swuu]

Please help I have a 4977 K 4920 D (slayers), followed the tut to the T and it hangs at boot up. I have already tried the UDE2 with no success. Is the default.xbe file in the UDE2 tutorial habibi signed, and is it suitable for UDE1. And if your kernal version is not in the fonts pack you use a generic one right?

[JMPovoa]

 That's what I did, and it works like a charm.

[swuu]

hey, i finnally got all the stuf fi need to odo this ltools guide, but how do you launch the ltools linnux menu

[BioWEB]

I wan't to make sure I've minimized all risks. The XBOX I''m currently trying to "change" has kernel 4817 (no problem) and dash 4817 (pre-live dash). Can I use UDE with this dash version ?
Will the XBOX allow to load the XBOX Live update.xbe from slayer's even though that's from a higher dashboard version 'cause I'm having some doubts with just copying the slayers C to this XBOX.
This Dash version has no fonts dir, but I need one for the UDE (when using updatefonts7). Just create the dir and away we go ?

If I can use UDE with this Dash, there would be the problem with the original Dashboard that looks for the font files in C root. Since this Dashboard has no fonts dir, I can't  HEX edit the current xboxdash.xbe because there are no references to \fonts\. What I did find were 3 references to XTF. If I rename the font files in the root to let's say .XFT, can I just change the 3 references found in the original dash to XFT to get the original Dash to load ?

Some info would be greatly appreciated !!!!!

Edit: since this is my first post on the forum, hi guys  

[JMPovoa]

swuu: you have to run it through a savegame exploit. This means, you have to have Mechassault, 007, or Splinter Cell 1, and you have to be able to transfer the gamesave to your Xbox harddrive. Then, you open the savegame on one of those games, and the installer boots up.

Bioweb: You should really give iTools a look, since it's the easiest and most foolprof softmod out there. And it works on any kernel and dash.

[swuu]

oh fuzzy balls. thats what i thought, i aint got neither one. back to sqaure one, what fonts do i need for 4977 k, and default.xbe do i need to get this to work.

[JMPovoa]

[BioWEB]

QUOTE (JMPovoa @ Aug 16 2004, 08:47 PM)

... Bioweb: You should really give iTools a look, since it's the easiest and most foolprof softmod out there. And it works on any kernel and dash.

Well, I've decided, what the hell, I'll just see if it works. Copied the HDD key to my own HDD, made sure the 007 + EvoX were still present and installed the UDE.

It works great. The only thing that didn't work was HEX edit the 4817 Dash to take .XFT fonts instead of .XTF ('cause this dash has it's fonts in C root I've renamed the original fonts to .XFT). When I tried loading the edited MODxboxdash.xbe through EvoX it showed the XBOX logo, then again it showed the XBOX logo and then EvoX popped back up. I'm not entirely sure, could also be a compatibility issue with the update.xbe from Dash 4920.

[swuu]

. But what was so irritating is that i did it b4 on a 4034 kernal, and it worked bootyful, so I wanted to do it on this one, but screw dat, I just got the ltools pack from the "usaual places", and put it together, I must say, its pretty idiot proof.......they dont even say press A, or B, it says press the BLUE button or the GREEN Button, what is this teletubbies? Thanx man this is the shiznit

[eh.]

QUOTE (BioWEB @ Aug 16 2004, 05:40 PM - part)

The only thing that didn't work was HEX edit the 4817 Dash to take .XFT fonts instead of .XTF ('cause this dash has it's fonts in C root I've renamed the original fonts to .XFT). When I tried loading the edited MODxboxdash.xbe through EvoX it showed the XBOX logo, then again it showed the XBOX logo and then EvoX popped back up. I'm not entirely sure, could also be a compatibility issue with the update.xbe from Dash 4920.

It's not a compatibility issue; they co-exist perfectly on my box (as follows) eh.  

The 4920 update.xbe(=>xboxdash.xbe) only uses the .xtf's in C:\fonts and the 4817 xboxdash.xbe(=>MODxboxdash.xbe) only uses the .xtf's in C:\.  Consequently you don't even need to hex the pre-live dash (nor rename the C:\ .xtf's) for it to co-exist.

Did you habibi sign the MODxboxdash.xbe?

[BioWEB]

QUOTE (eh. @ Aug 17 2004, 05:09 AM)

It's not a compatibility issue; they co-exist perfectly on my box (as follows) eh.   The 4920 update.xbe(=>xboxdash.xbe) only uses the .xtf's in C:\fonts and the 4817 xboxdash.xbe(=>MODxboxdash.xbe) only uses the .xtf's in C:\.  Consequently you don't even need to hex the pre-live dash (nor rename the C:\ .xtf's) for it to co-exist. Did you habibi sign the MODxboxdash.xbe?

No, don't have to. I'm using UDE to load NKPatcher and then EvoX Dash 3935.
Wouldn't it give a 21 if I've tried loading an unsigned MODdash ? Even so, NKPatcher allows me to run unsigned code anyway. Did it with my own 4817/5105 too and I can get back to the MS Dash on my box without ever having signed that MODdash after HEX-ing it.

And you say I can leave the XTF files in the original root ? 'Cause I thought you could end up with a frozen box when you leave the XTF's in the root.

No wait, as you say, this Dash version ONLY searches for fonts in the root... Could that be a benefit on pre-live Dashboards ? Not even having to hex the MODdash ? But then again, why do you have to delete all font files in C Root with live dashes ? 'Cause the way I see it, these root fonts only affect the UDE exploit.

[eh.]

@BioWEB: Apologies... I now realize that my feedback probably wasn't relevant or helpful for you eh.

I'd forgotten this method doesn't use the C:\fonts directory (as it's renamed to C:\f0nts).  That results in non-hex'd live dash xbe's (such as the UDE's bootstrap) getting their .xtf's from C:\ instead.  Additionally, although I use UDE and the 4817 dash, my setup includes both C:\fonts (for the bootstrap) and C:\f0nts (for a hex'd live dash).

[PedrosPad]

QUOTE (eh. @ Aug 17 2004, 05:09 AM)

The 4920 update.xbe(=>xboxdash.xbe) only uses the .xtf's in C:\fonts and the 4817 xboxdash.xbe(=>MODxboxdash.xbe) only uses the .xtf's in C:\.

Minor correction:

Dash 4290 checks C:\fonts first, then C:\ for it's fonts.
Dash 4817 does only check C:\.

[eh.]

(
The context was "on my box (as follows) eh." plus in the message preceding yours I added...

QUOTE

I'd forgotten this method doesn't use the C:\fonts directory (as it's renamed to C:\f0nts). That results in non-hex'd live dash xbe's (such as the UDE's bootstrap) getting their .xtf's from C:\ instead.

)
Glad to see you're still keeping a watchful eye over your baby though - thanks again for it eh.