Post by: ldots on June 04, 2004, 02:34:00 AM
Initial version : 1.0
Current version : 1.3
NOTE. From version 1.3 this package was wrapped in a graphical front-end provided by MXM. The linux toolbox is still available (and unchanged) when running the 'Run-linux' option of this MXM menu. This MXM menu was created to make it easier to install/uninstall UDE without the use of a telnet connection from a PC. The linux toolbox is still very useful though, as many of the tools included are not available from the MXM menu. The description below still applies for the linux toolbox.
For information no the graphical interface look here
------------------------------------------------------
I have put together a memory-card package that runs a mini-linux distribution on the xbox, and offers a bunch of useful tools for xbox modders. I called it ltools and the package should be available "the usual places". Hope the following features make you interrested : UDE package with install/uninstall options, hdkey & eeprom backup, dashboard patcher, xbedump, restoring C from compressed image made by UDE installer or c-backup command. Running the package from an exploitable game should work on any xbox (regardless of dash and kernel version), as long as the exploitable game is the correct/original version. The UDE installer will only be compatible with kernel versions up to and including 5530 (running PBL only works on kernel versions below 5530).
As always - use the info and tools described here at your risk. Don't come whining if something goes wrong...
Some of the tools a homemade, but most credit goes to the xbox-linux project for offering so many useful tools and information. We cannot thank these guys enough
Things to know about the package
- You don't have to be a linux-guru to use this
- Use this mini-linux if you find the included tools useful. Also consider it as a way to access and manipulate your files directly on the xbox, if you like me feel that an ftp connection through Evox or similar is too limiting. If you are a bit familiar with linux you will appreciate being able to edit/configure/sign stuff directly on the xbox. If you have no intension of doing this just issue the userfriendly commands (look further down for a list). The minilinux includes both an telnet and ftp server.
- This was initially intended as a memory card package, and is distributed ready for the Action Replay software. If however you have gained ftp access to your xbox some other way and do not have a memcard, you can unzip the package and upload it manually. Running the mini-linux can then be achieved by adding the game save dir holding the package to your search path in evox or any other dash, or by extracting the included Evox and using this to lauch the mini-linux. This Evox will automatically be installed when running the UDE installer.
- The package requires you have a network connection to the xbox, since the tools included are executed from a telnet connection. Some might not like this, but at least it means people have no excuse for not ftp'ing the eeprom/backup to the PC
- The UDE installer/uninstaller runs from the mini-linux. Therefore if you disable the UDE, for playing live, you need to have a way to rerun the mini-linux to re-enable the UDE. I released this as a game save package to let users to this by using an exploitable game. Alternatively one could modify the setup to use the Easter Egg Exploit or audio hack to rerun the mini-linux and re-install the UDE.
Download the package and transfer to your xbox either by a memory card, by ftp or by hotswapping. If you choose the hotswapping option have a look at
xboxhdm and maybe also consider the UDE package for xboxhdm instead. If you use a memcard, as always have in mind that Action Replay cards are known to corrupt large saves. These packages have been tested by ftp'ing them to an xbox, so if they dont work for you after using a memcard, corruption is the likely cause
Once installed launch the mini-linux by either trickering the game save hack through an exploitable game, or by launching the linux bootloader (E:\UDATA\xxxxxxxxx\xxxxxxxxxx\default.xbe, x's depends on whether you use the MA or SC package).
Once running the xbox is not of much use (an usb keyboard should be useable, but I havent tried). Go to your PC. Open a DOS prompt and type :
| CODE |
telnet 192.168.0.3 login : root pass : xbox |
You will then be presented with a list of the tools in this package. You run these tools by siply typing the command name and hitting Enter. Just like a DOS prompt. The first time you run this package I advice you to run the 'backup' option and ftp the output to your PC (see below).
The tools
You will see this screen on login :
| CODE |
*********************************** Welcome to this mini-linux for Xbox *********************************** Connect to your xbox with telnet or ftp : User : root Password : xbox IP : 192.168.0.3 Netmask : 255.255.255.0 The following xbox relevant tools are available : backup : Make backup of HDD password and eeprom c-backup : Make compressed image of C-drive c-restore : Rebuild C-drive from previous backup UDE : Install/Uninstall the Ultimate Dashboard exploit dashversion : Determine dashboard version of an xboxdash file patcher : Patch xtf or fonts strings in xboxdash file xbinfo : Print varios information on your xbox (used by backup) xbedump : Sign an xbe (only habibi key at the moment) raincoat : Do not use unless you know what you are doing #### TO BE GENTLE ON YOUR HDD PLEASE RUN : shutdown #### BEFORE RESETTING YOUR XBOX |
Explanations :
- backup : Makes backup of eeprom and HDD password to E:\backup_linux folder. Run this option on your first login and ftp the backup_linux folder to your PC. Also consider running the command below for a backup of C:
- c-backup : Make compressed image of the entire C-drive. A rough estimate is that a 100 MB file is created in E:\backup_linux. With this backup on your xbox you will be able to restore your C-drive using the c-restore command. This could be usefull if you or Xbox Live "corrupted the C-drive.
- c-restore : Rebuild C: from compressed image genrated by c-backup. The backup is checked for authenticity. Most usefull if the C-backup is functional
- UDE : Takes an argument (-install or -uninstall), to do just that to the Ultimate Dashboard Exploit. It also installs :
- Evox v. 3935
- Optionally PBL 1.4.1, using the 4981.67 bios (modified to load E:\Evox\default.xbe as the primary dash). If you have kernel 5530 or above, answer 'no' when asked whether to install PBL
- Evox v. 3935
- If PBL is installed you have the option to install a patched copy of the MS Dash on C: (the reason PBL is required is that xbedump doesn't seem to want to sign xboxdash.xbe).
- Repack the memory-card package and include the update.xbe in the UDATA\xxxxxxxxx\xxxxxxxxxx\files folder, and rezip it.
- Install the package as it is and ftp the update.xbe to the xbox (E:\UDATA\xxxxxxxxx\xxxxxxxxxx\files) once you run the package and thereby has ftp-access.
Size : 1974272 bytes
MD5SUM : 8ab653c39f555758fb65d9014928c4cd
It's available on some live 1.0 enabled games, not all, and on Slayers Evox 2.5 Final. The UDE installer will check the md5sum of the update.xbe and abort if it doesn't match, to hopefully avoid non-functional installs. - dashversion : Takes a dashboard xbe as its argument and displays the version.
- patcher : Patch a dashboard xbe to look for *.bak fonts or to look in C:\f0nts. The output will be a renamed copy (msdash.xbe). The included Evox is setup to run this MS Dashboard.
The patcher can be used on any version of dashboard (and tHC if wanted), since it does a search for the bytes to patch ratcher than patching fixed offsets. - xbinfo : Print various information on your xbox. HDD key, HDD password, etc.
- xbedump : Sign an xbe. Currently only with the habibi key. Audio and font will be included.
- raincoat : Use with caution. Can be used for TSOP flashing if the TSOP has been write enable by soldering some points on the mobo. It's the unofficial v0.70 which supports a lot of chips.
Hope you will have fun with this toolbox
Post by: ldots on June 04, 2004, 02:41:00 AM
chimpanzee, I didn't forget about your idea of making a ncurses based graphical interfase for this package, that you posted on the UDE thread. I dont think this is desirable since using the xpad linux driver (for using the controller as a mouse) will require running an X-server. This would make the package explode - an make it unsuited for a memcard. Maybe for an extended version though.
Post by: GRID on June 04, 2004, 03:36:00 AM
Post by: GRID on June 04, 2004, 03:55:00 AM
Post by: chimpanzee on June 04, 2004, 07:00:00 AM
| QUOTE (ldots @ Jun 4 2004, 11:41 AM) |
| Let me have the first reply chimpanzee, I didn't forget about your idea of making a ncurses based graphical interfase for this package, that you posted on the UDE thread. I dont think this is desirable since using the xpad linux driver (for using the controller as a mouse) will require running an X-server. This would make the package explode - an make it unsuited for a memcard. Maybe for an extended version though. |
I am looking into the possibility of this. I don't think X is needed as the Xpad has both a joystick and mouse driver and there are some joystick-to-keyboard mapping stuff. What I am looking for is a scriptable interface(hopefully shell script, as perl/python would be much larger) for ncurses but still be able to fit inside the 8M memory card.
For my personal use, since I got the 128M jump drive secure(only thing I could find when I first started the sofmod route), I would put all three game save on it :-)
Thanks for the packages.
Post by: GJCD on June 04, 2004, 09:16:00 AM
It says...can't acess to tty or something like this.
What could be?
Thanks
Post by: chimpanzee on June 04, 2004, 09:29:00 AM
| QUOTE (GJCD @ Jun 4 2004, 05:40 PM) |
| When I run default.xbe, linux starts and a little after it stops. It says...can't acess to tty or something like this. What could be? Thanks |
um, sounds like the kernel is compiled without VGA console support or the console device node is not in /dev/. My quick fix was just enable the VGA console support which xbox-linux's sample config doesn't have. Unfortunately, either you need to do the compilation yourself or wait for Idots to redo the package.
Post by: GJCD on June 04, 2004, 09:44:00 AM
Post by: GRID on June 04, 2004, 10:32:00 AM
This post has been edited by GRID: Jun 4 2004, 05:33 PM
Post by: ldots on June 05, 2004, 12:33:00 AM
| QUOTE (GJCD @ Jun 4 2004, 05:40 PM) |
| When I run default.xbe, linux starts and a little after it stops. It says...can't acess to tty or something like this. What could be? Thanks |
This is all OK. Linux is running just fine. You do see the text on the TV dont you?
As I wrote in the tutorial, at that point it is time to leave your xbox and turn to your PC to make a telnet connection.
To connect to the xbox, you can have either a direct connection with a crossover cable or have the xbox and your PC hooked up to a router or switch.
When connection to the xbox I have my PC setup as :
IP : 192.168.0.1
netmask : 255.255.255.0
telnet to the xbox with :
login : root
pass : xbox
On login you get the info screen.
Post by: ldots on June 05, 2004, 12:36:00 AM
| QUOTE (GRID @ Jun 4 2004, 06:56 PM) |
| im gettign this too i cant telnet in or anything either, i thought I had my network settings messed up because the rest of the network is 192.168.7.* but i guess thats not the problem. |
192.168.7.* will not do because the netmask is 255.255.255.0
Your PC and your xbox is not on the same subnet! Read my post above.
Post by: GJCD on June 05, 2004, 01:04:00 AM
IP : 192.168.1.2
netmask : 255.255.255.0
How can I connect?
Thanks Idots
Post by: ldots on June 05, 2004, 01:05:00 AM
| QUOTE (GJCD @ Jun 5 2004, 09:28 AM) |
| My PC has: IP : 192.168.1.2 netmask : 255.255.255.0 How can I connect? Thanks Idots |
Try changing to your PC to :
IP : 192.168.0.1
netmask : 255.255.255.0
Then do the telnet 192.168.0.3
Post by: GJCD on June 05, 2004, 01:17:00 AM
Is there another way to do this?
Post by: ldots on June 05, 2004, 01:22:00 AM
Post by: chimpanzee on June 05, 2004, 12:49:00 AM
Post by: ipodder2003 on June 05, 2004, 04:09:00 PM
Post by: morpheous1777 on June 05, 2004, 06:30:00 PM
Post by: ldots on June 05, 2004, 11:06:00 PM
I put Evox on E: in a folder, as I like to keep things tidy. Personaly I dont like all sorts of files floating around in the root of C: or E:
Therefore the bios included loads E:\Evox\default.xbe as its primary dash.
Bert-ate-Ernie has been modified to load E:\pbl\pbl.xbe
So to replace the bios included, either edit the bios in xbtool or move the Evox installation to the root of C: (renaming the default.xbe to evoxdash.xbe).
Post by: chimpanzee on June 05, 2004, 11:48:00 PM
| QUOTE (ldots @ Jun 6 2004, 08:06 AM) |
| OK, I updated the tut. to mention these things. Thanks for the feedback. I put Evox on E: in a folder, as I like to keep things tidy. Personaly I dont like all sorts of files floating around in the root of C: or E: Therefore the bios included loads E:\Evox\default.xbe as its primary dash. Bert-ate-Ernie has been modified to load E:\pbl\pbl.xbe So to replace the bios included, either edit the bios in xbtool or move the Evox installation to the root of C: (renaming the default.xbe to evoxdash.xbe). |
Um, won't that be too PBL specific pointing to e:\pbl\pbl.xbe especially when some kernel would have problem loading it ? e:\default.xbe seems to be more neutral.
Post by: ldots on June 06, 2004, 12:28:00 AM
| QUOTE (chimpanzee @ Jun 6 2004, 08:48 AM) |
| Um, won't that be too PBL specific pointing to e:\pbl\pbl.xbe especially when some kernel would have problem loading it ? e:\default.xbe seems to be more neutral. |
Yes, it's PBL specific. The UDE part of the package is aimed at pre-5530 users. 5713+ users cannot run the update.xbe, so the "only" potential users who cannot use this are 5530 users.
The whole point of making a package was to provide an automatic install that doesn't give the user too many options. If you wanted to "experiment" (boot anything besides PBL on startup) I guess you wouldn't be using a package anyway.
But if anyone would like it - I could modify the UDE tool to make the installation of PBL optional, and if the user chooses not to install PBL, bert-ate-ernie could boot E:\default.xbe (evox) instead. Would that be better ?
Post by: chimpanzee on June 06, 2004, 01:07:00 AM
Post by: ldots on June 06, 2004, 07:55:00 AM
Post by: Dan Wysocki on June 06, 2004, 12:08:00 PM
Post by: ipodder2003 on June 06, 2004, 01:41:00 PM
Post by: spongy on June 06, 2004, 09:01:00 PM
I downloaded ltools,transfered it to my HDthe same way I do all my gamesave exploits and installers(homemade usb to controller to M$ memory card).loaded MA>campaign>Run Linux...The LED turns orange the screen flickers red then goes black, then after 10 or 15 seconds the LED flashes orange and the box shuts down.
What am I doing wrong here?
Thanks
EDIT: forgot to say, it's a clean V1.0 with C: from slayers 2.5
Post by: ldots on June 06, 2004, 11:32:00 PM
I just re-tried the package by ftp'ing it to a v1.0 xbox. Ran perfectly fine.
Only thing I can think of is that the package got corrupted on transfer. I would suggest trying this :
Get another MechAssault game save hack that just has Evox on it. Run this hack to get ftp-access. Once in, delete the E:\UDATA\4d530017 folder and upload the same folder from the ltools package. Try running the MA->Campaign->Run Linux hack again. If this works it's very likely that corruption was the cause of your problems.
Some memory cards have problems handling large game saves. My memcard has previously worked fine with large game saves (even though it's an Action Replay card), but when testing these ltools packages I did run into the corruption problem a few times. So if the ltools packages do not work, either try another memcard, or try getting ftp-access with a small game save with evox, and ftp the ltools to the xbox instead.
Post by: spongy on June 07, 2004, 05:09:00 AM
| QUOTE (ldots @ Jun 7 2004, 01:32 AM) |
| Get another MechAssault game save hack that just has Evox on it. Run this hack to get ftp-access. Once in, delete the E:\UDATA\4d530017 folder and upload the same folder from the ltools package. Try running the MA->Campaign->Run Linux hack again. If this works it's very likely that corruption was the cause of your problems. |
Bad news... I did as you said, ftp'ed the save in, but with the same results.
Any more suggestions?
Thanks again.
Post by: ldots on June 07, 2004, 05:33:00 AM
OK - just brainstorming here :
- Does your xbox run fine otherwise - have you had any HDD troubles?
- Is it a stock HDD?
- When you ftp'ed the hack in, did your run Evox from a Mech game save hack? The reason I ask, is that I heard that for some people who has been on live with MA the hack stopped working. Most likely because some updates are downloaded that patches the flaw in MA. If you can run the Evox game save hack, that's not the problem though,. Related question, you do have the exploitable MA version right?
- If it is MA related then you should be able to 'Run linux' from Evox. You could try this by extracting the Evox included in the ltools package and using this. It adds a 'Linux' item to the 'Launch Menu -> apps'
You do have this file-structure in the UDATA folder right?
| CODE |
4d530017/ SaveImage.xbx TitleImage.xbx TitleMeta.xbx 62D648EBF155/ MASave.sav SaveMeta.xbx default.xbe files initrd linuxboot.cfg vmlinuz xbsavegame.dat |
Post by: spongy on June 07, 2004, 08:38:00 AM
| QUOTE |
| Does your xbox run fine otherwise - have you had any HDD troubles? |
Xbox runs great otherwise,both stock and exploited(I've used audio,font and most recently the DD exploit).- no HDD troubles at all.
| QUOTE |
| Is it a stock HDD? |
Stock HDD (never unlocked)
| QUOTE |
| When you ftp'ed the hack in, did your run Evox from a Mech game save hack? The reason I ask, is that I heard that for some people who has been on live with MA the hack stopped working. Most likely because some updates are downloaded that patches the flaw in MA. If you can run the Evox game save hack, that's not the problem though,. Related question, you do have the exploitable MA version right? |
MA is the only way that I have to MOD my box.I have never connected MA to live.I deleted all MA gamesaves before adding this.
| QUOTE |
| If it is MA related then you should be able to 'Run linux' from Evox. You could try this by extracting the Evox included in the ltools package and using this. It adds a 'Linux' item to the 'Launch Menu -> apps' |
I'm not sure what you mean here
so I tried this: I extracted your gamesave and went to udata / 4d530017 / 62D648EBF155 / files,extracted evox and moved the "three files" to / 62D648EBF155 /. When I tried to run remoteX from evox it started to go to the loading screen,then jumped right back to evox.I also tried adding the three files to mechassaultwithevox gamesave with the same result.| QUOTE |
| What is really strange is that the LED does turn orange indicating that the linux boot loader does run? |
Yes, When I load your gamesave(as is) to the HDD. I boot MA>campaign>Run Linux...the LED instantly turns orange,the box goes quiet,about ten second later the LED starts flashing orange,the HDD spins up a few times,and the box just shuts down.
That is the exact file structure except I also have an evox.ini in 62D648EBF155/
| QUOTE |
| um, sounds like the kernel is compiled without VGA console support or the console device node is not in /dev/. My quick fix was just enable the VGA console support which xbox-linux's sample config doesn't have. Unfortunately, either you need to do the compilation yourself or wait for Idots to redo the package. |
I didn't really understand this.Could this be my problem too?Can I try to launch this from another exploit? DD or audio? and still be able to install UDE?
Thanks again
Post by: chimpanzee on June 07, 2004, 08:46:00 AM
Post by: ldots on June 07, 2004, 09:06:00 AM
| QUOTE (spongy @ Jun 7 2004, 05:38 PM) |
| Can I try to launch this from another exploit? DD or audio? and still be able to install UDE? |
That was sort of what I was suggesting with extracting the evox from my package. OK, try doing it this way :
- unzip the ltools package.
- get ftp access with your mechassaultwithevox hack.
- create a folder on E: called ltools
- Put everything inside the 62D648EBF155 folder of my package on E:\ltools
- Edit the evox.ini for your mechassaultwithevox hack to look for apps in E:\ltools by adding the line
| CODE |
| AutoAddItem "e:\ltools" |
to the "apps" section of you evox.- ftp this edited mechassaultwithevox game save to your xbox (E:\UDATA)
- Run MA -> Campaign -> Run Linux
- Once Evox runs you should have a "Linux" option the the "Launch Menu -> Apps" section.
-
Title: Memory-card, Linux-based Toolbox
Post by: ldots on June 07, 2004, 09:24:00 AM
-
Thinking about it, it seems more likely that some of the files have been corrupted somehow - from transfer, extraction,... what do I know?
Because the boot loader does run (LED color changes), meaning that the MA hack must be trickered. Maybe try re-downloading the package, maybe try another tool to extract the package, maybe even try the initial release (look in the _old folder at 'the usual places'). As i said it runs fine on my v1.0 (and v1.4).
-
Title: Memory-card, Linux-based Toolbox
Post by: spongy on June 07, 2004, 10:02:00 AM
-
Post by: ldots on June 07, 2004, 09:24:00 AM
Because the boot loader does run (LED color changes), meaning that the MA hack must be trickered. Maybe try re-downloading the package, maybe try another tool to extract the package, maybe even try the initial release (look in the _old folder at 'the usual places'). As i said it runs fine on my v1.0 (and v1.4).
Post by: spongy on June 07, 2004, 10:02:00 AM
| QUOTE (chimpanzee @ Jun 7 2004, 10:46 AM) |
| do you have the original MechInstaller ? I would suggest to replace the linux files(vmlinuz/initrd) with that to first isolate if it is related to it or something else. |
Post by: ldots on June 07, 2004, 10:09:00 AM
Post by: spongy on June 07, 2004, 11:02:00 AM
| QUOTE (ldots @ Jun 7 2004, 12:09 PM) |
| Hmmm, so it boots with an older kernel/initrd. Only thing is with these old version you wont have my tools available (like the UDE installer). |
your tools were what I wanted
| QUOTE |
| Are you saing you also tried the _old versions of ltools and that didn't work either? |
Yes I tried the old version of ltools.
| QUOTE |
| If so, then for some reason the new kernel is not compatible with your xbox? But why? It works on my v1.0 |
I hope you're not asking me Anyway, Don't worry about it too much as I have other ways into my box.I'm doing this mostly for fun(and the ease of use
) Not one other person has had this problem. We should definitly assume it's my fault until there's more reports of it.I'll keep messing with it and keep you updated.
Thanks again
EDIT:spelling
Post by: ldots on June 07, 2004, 11:17:00 AM
But it would be nice to know what causes your problems. At the moment the only thing I can think of is that your "old" (no offense) xbox has some hardware not supported by the kernel in my package, but supported by the old kernel on the MechInstaller. Using that old kernel is not an option though as it doesn't have focus support.
Post by: ldots on June 07, 2004, 12:58:00 PM
Could you try to make a clean copy of my package again. Then extract the code below with Iceows, and try replacing the linuxboot.cfg of my package with the ones from the archive below and see if that makes you xbox boot the kernel in my package. I suspect the problems with your specific xbox is related to the framebuffer driver.
| CODE |
begin 644 test.tgz M'XL(`&CEQ$```^W52VZ#,!0%4(]9Q=M`P79L4`>L)<+@5!8$B/DHS>IKPJ!2 MJK:J*AI5N6=B/I9L_-X5<<(VQ[GBF=9AO+H=K]>"\U2(5.K=+CS/,B$9Z>VW MQM@TC(4G8K[KQJ_F???^GXJ3QK73V82OB\O#RUYLL`9?BJO4I_677+W77X0^ M$3*5&2.^P5X^>/#ZU]:WMJ'YN+3!)7*M&WU%ZQ`5?6_;]2Y?^\27M!Q$GE1V M3GQQY-27+C>N&YP_46VJ)V\'.U)HJ',^]4U75!2F56ZH]Z;IRGIP%YLK_IQ2 MM,PY&&JC>Y_!([O-O]Q@C9_D7^DU_^$W@/S_@3OFW[NY"/E_1?X!```````` 3``````````!^Z0U\$346`"@````` ` end |
To everybody else. I think this is a rare case, so please go ahead and try the package. More reports on succes or failure are very welcome.
Post by: spongy on June 07, 2004, 03:08:00 PM
Is it two different .cfg files?
EDIT: I'm not sure I'm doing it right but I keep ending up with "linuxboot.CFG_1" and "linuxboot.CFG_2". These won't load so copied the text from one over the text in the original "linuxboot.cfg". No dice, tried the other same result. Flashing orange then shutdown.
Post by: ldots on June 08, 2004, 06:27:00 AM
Until I figure out why there is an incompatebility issue with your specific xbox (though it's hard to debug when I cannot generate the problem myself ?), I would like you to try a custom package made for these problematic box's.
PM'ed you with details.
Still think it could be the framebuffer driver since that changed between the MechInstaller kernel and the kernel in my package. That's also supported by the fact that the crash occurs early in the boot proces, and that the screen is all garbled.
Post by: ldots on June 08, 2004, 08:06:00 AM
Try to just get ftp access using a Mechassault-with-evox game save hack and ftp the extracted package to E:\UDATA to eliminate the possibility of the package being corrupted by the memcard.
Also :
- make sure you have no other files besides bert-ate-ernie.xtf with the *.xtf extension in the root of C: (that is when the hack is installed, when not installed you should have nothing but the original XBox Book.xtf and Xbox.xtf files there).
- make sure the fonts folder only contains the original *.xtf files (XBox Book.xtf and Xbox.xtf)
- make sure you have no folders called Evox and pbl in the root of E:, or answer 'y' when the UDE intaller asks you whether you want to replace the current Evox and pbl installations.
Post by: ldots on June 08, 2004, 10:20:00 AM
But nice to know your experiences. I will try to make the installer even more aware of previously installed hacks.
Post by: spongy on June 08, 2004, 03:37:00 PM
Might I add what a GREAT package this is.Very simple and fast.I had a backup of eeprom / HDD password,a backup of C:,and had the UDE installed with a link to M$ dash in no time.Haven't had time to mess with everything(-uninstall,c-restore).
So I have a few questions.I assume the fastest way to get back to a Live! state would be UDE uninstall ?
Or would it be c-restore?
Can I use these from UDE or do I need to run the gamesave each time ?
According to the poll on the home page 42% of people who voted so far have a 1.0 box.So there might me a few more cases like mine.Until then I will feel special "ldots made a package just for me"
Keep up the good work and thanks again
Post by: ldots on June 09, 2004, 02:48:00 AM
| QUOTE (spongy @ Jun 9 2004, 12:37 AM) |
| According to the poll on the home page 42% of people who voted so far have a 1.0 box.So there might me a few more cases like mine. |
Glad it worked out.
Apparently not all v1.0 boxes have the problems you have, so time will show how many users experience this. In any case you should also find this "replacement package" at the usual places now - with a note to try the standard packages first, and if these dont work try the replacement.
| QUOTE (spongy @ Jun 9 2004, 12:37 AM) |
So I have a few questions.I assume the fastest way to get back to a Live! state would be UDE uninstall ? Or would it be c-restore? Can I use these from UDE or do I need to run the gamesave each time ? |
UDE -uninstall is the fastest way to get to an unmodded state. c-restore will uncompress the image of C, so that takes a bit of time (roughly 30 secs. or so). You dont have to run UDE -uninstall from the game save though. You can just run the mini-linux from Evox (should show in the apps menu). For re-enabling the UDE you have to use the game save hack though, or setup the Easter Egg exploit yourself. I thought about including an Easter-Egg switcher, but decided not to :
- The EE exploit will most likely have a limited lifetime.
- It would require people to pack one more 'correct' xbe (the prelive dash) and maintain another set of hacked fonts.
Post by: ldots on June 09, 2004, 03:02:00 AM
the major change is that the UDE installer should be more aware of previously installed hacks and fonts.- If the installer finds Evox or PBL on E: (case-insensitive), the user will be prompted if its ok to replace these installations with the ones from this package. The user is prompted, but I recommend answering 'y' to this question.
- After renaming Xbox.xtf and XBox Book.xtf in C: and the fonts folder, the installer will check for other occurances of *.xtf in the root of C: and back them up in an xtf_backup folder. Previously installed hacked fonts could interfere with the UDE.
- It should be safe to run UDE -install continuously. The installer will see that UDE is allready installed and take the nessecary precautions when re-installing.
- UDE -uninstall will check that it is possible to revert to a working unmodded state. If the nessecary files are not found, the uninstall will be aborted.
Post by: ldots on June 09, 2004, 08:05:00 AM
If you allready have the game save on the HDD and your clock is set (your xbox has not been unplugged for more than a few hours), then you should be able to load the mini-linux from SC and either use UDE to reinstall the hack or use c-restore to revert your C-drive to what it was like before you installed the hack.
If you havent got the game save on the HDD and cant boot to your MS dash, then you have to hotswap!
Post by: grapp on June 09, 2004, 02:24:00 PM
Sorry but i can't find ltools to download from anywhere.
Did the name change or can somebody give me a hint?
thx
Post by: Jace_100 on June 09, 2004, 10:40:00 PM
I am looking under Exploits/Packages/UDE and I don't see anything
Post by: ldots on June 09, 2004, 10:43:00 PM
Look here
A hint : It's for the 'XBOX', its an 'Operating System', its 'linux'
Post by: grapp on June 09, 2004, 11:20:00 PM
thx again
Post by: FBF on June 11, 2004, 01:05:00 AM
Post by: ldots on June 11, 2004, 01:22:00 AM
Post by: chaotik on June 11, 2004, 05:30:00 AM
Post by: ldots on June 11, 2004, 06:01:00 AM
All commands of this package will work out of the box, but the UDE installer needs the correct version of the update.xbe. So for the UDE command, the update.xbe is not optional! If it is not found the installation is aborted, as you have seen. You cannot get the hack running without the correct update.xbe (md5sum is checked to verify it's the right version). I could not add the update.xbe without breaking the rules of 'the usual places'.
So leave everything as it is in the package - only add update.xbe to the E:\UDATA\xxxxxxxxxxx\xxxxxxxxxxx\files folder.
Post by: ldots on June 11, 2004, 06:13:00 AM
| QUOTE (old engineer @ Jun 11 2004, 03:08 PM) |
| ...Trouble is I'm using the update.xbe off the slayer's disc !!!!!!!!!!!!!!!!!! |
And it's Slayers version 2.5 Final ?
Anyway, if it (or any files called update.xbe) is in the files folder you would not get the "Cannot find ..." error. You would get the md5sum of the update.xbe you put there and the expected/correct md5sum.
| QUOTE |
| But thanks for explaining about what needs raring and what can be left as is. |
Nothing needs raring. I would start from a fresh copy of ltools_*.zip and only add update.xbe
Post by: ldots on June 11, 2004, 06:51:00 AM
Did you delete the old E:\UDATA\4d530017 folder and started from a fresh copy ?
Then upload the update.xbe to E:\UDATA\4d530017\62D648EBF155\files
Linux is case-sensitive, so it should be update.xbe, not update.Xbe or Update.xbe or, .... (you get the picture).
If it still doesn't work please post the exact erro message and try to do the command : ls -l /mnt/E/UDATA/4d530017/62D648EBF155/files
from the telnet connection and post the output.
You can get the md5sum of the files by doing :
md5sum /mnt/E/UDATA/4d530017/62D648EBF155/files/update.xbe.
Post by: ldots on June 11, 2004, 07:31:00 AM
Are you absolutely sure you upload it to the folder listed in the error-message.
Try the : ls -l /mnt/E/UDATA/4d530017/62D648EBF155/files/
command, when in linux, and write down the output.
Something most be going wrong when you ftp in the file.
Post by: ldots on June 11, 2004, 08:10:00 AM
Your prompt is fine. Only possible explanation is that the file-permissions on your E-drive are strange/wrong.
When booting to the mini-linux, try running :
chmod -R 755 /mnt/E
Then retry the : ls -l /mnt/E/UDATA/4d530017/62D648EBF155/files
If that does not list the directory content, then retry it going one directory down at a time :
ls -l /mnt/E/UDATA/4d530017/62D648EBF155
ls -l /mnt/E/UDATA/4d530017/
etc.
I just tried the package on my xbox. Uploaded update.xbe, UDE installed fine.
Post by: old engineer on June 11, 2004, 08:55:00 AM
Quality job!
U would not believe what I did wrong, please dont shout
...Through all the deleting and installing I must of deleted update.xbe from the UDATA folder on E:
...Trouble was I still had a copy of it in my ltools folder on E:, hence I thought I must still have a copy in the right place!!!!
It really started to dawn on me as the commands in linux showed that it definitely wasn't listed step-by-step/folder-by-folder.
Transferred it over and ....well u know the rest
Post by: ldots on June 11, 2004, 09:03:00 AM
I'm not gonna shout
, just delete the post I was gonna submit with even more suggestions.Phew, nothing wrong with the installer then. I knew from the beginning that having the user add the update.xbe themselves could cause some trouble, but it had to be done this way...
Post by: DonaldMCRonald87 on June 11, 2004, 09:32:00 AM
Post by: DonaldMCRonald87 on June 11, 2004, 09:50:00 AM
Post by: ldots on June 11, 2004, 01:27:00 PM
| QUOTE (old engineer @ Jun 11 2004, 06:39 PM) |
| Right now it works, and works lovely, just wondered if u could explain whats happening as you fire the Xbox up, I understand so much then my eyes glaze over lol. |
The UDE exploit is different from other dashboard exploits in that is doesn't actually use the xboxdash.xbe to gain control over the xbox, and the MS dashboard is not nessecarely reached on boot like with the Mech fonts. The UDE exploit uses the update.xbe. So on boot update.xbe is loaded (since this is renamed to xboxdash.xbe). This looks for *.xtf fonts. Finds Bert-ate-Ernie. The exploit trickers -> patches the kernel in memory to use the habibi key and loads a habibi signed xbe.
This can be Evox or PBL depending on what you choose in the installer.
Loading Evox directly we still run the retail BIOS, only the key has been replaced with the habibi key. So if we wanted to run MS dash from Evox we would have to hexedit the MS dash to look for the original fonts and sign it with the habibi key. xbedump doesn't seem to want to sign the MS dash
so this is not possible in this setup.If we run PBL from the UDE exploit we load a hacked bios that has the signature check disabled entirely. Therefore from PBL any unsigned xbe can be run. The replacement BIOS has a default dashboard it will load. In your case Evox. From Evox we can run the hexed MS dash since signature checks have been disabled.
Hope I answered some of your questions
Post by: DonaldMCRonald87 on June 11, 2004, 01:54:00 PM
Post by: ldots on June 11, 2004, 02:03:00 PM
Post by: DonaldMCRonald87 on June 11, 2004, 02:04:00 PM
Post by: ldots on June 11, 2004, 02:13:00 PM
,but find your network device in the control panel. Right click on your network interface and enter the properties. Find the TCP/IP setting and change to :
IP : 192.168.0.1
Netmask : 255.255.255.0
Take note of what your settings are now if you want to revert them later (probably set on automatic/dhcp).
Post by: DonaldMCRonald87 on June 11, 2004, 02:18:00 PM
Post by: DonaldMCRonald87 on June 11, 2004, 02:32:00 PM
telnet [-a][-e escape char][-f log file][-l user][-t term][host[port]]
-a attempt automatic logon. same as -l option except uses the currently logged on user's name
-e escape character to enter telnet client prompt
-f file name for client side logging
-l specifies the user name to log in with on the remote system. requires that the remote systeom support TELNET ENVIRON option.
-t specifies terminal type supported term types are vt100, vt52, ansi and vtnt only.
host specifies the hostname or ip address of the remote computer to connect to
port specifies a port number or service name.
Post by: ldots on June 11, 2004, 02:34:00 PM
| QUOTE (DonaldMCRonald87 @ Jun 11 2004, 11:32 PM) |
| when i change the ip and subnet mask and then type telnet 192.168.0.3 login : root pass : xbox i get something like this |
You dont punch it all in on one line do you?
First : telnet 192.168.0.3
Then the xbox should ask your for the login :
type root
etc.
Post by: DonaldMCRonald87 on June 11, 2004, 02:36:00 PM
Post by: ldots on June 11, 2004, 02:40:00 PM
- If you have a direct connection from the PC to the xbox, you must use a crossover cable.
- Make sure your PC network setting are as required.
- Make sure you have no firewall running on the PC.
Post by: DonaldMCRonald87 on June 11, 2004, 02:43:00 PM
Post by: DonaldMCRonald87 on June 11, 2004, 02:50:00 PM
Post by: ldots on June 11, 2004, 02:59:00 PM
| QUOTE (DonaldMCRonald87 @ Jun 11 2004, 11:43 PM) |
| i did all that but it still isnt working... |
Well, it's your network that's not set up correct! Double check the settings. Need more info on how your PC-Xbox connection is set up (hardware-wise) if you need more help. Direct/switch/router?
From the DOS prompt can you 'ping' yourself ?
C:\> ping 192.168.0.1
With repect to your HD. More info needed. How did you build this HDD. Sure all cables are firmly attatched. IS the jumber set on 'cable select'
Now I have really got to get some sleep. I my part of the world it's very late, and I have a loooong day at work tomorrow.
Post by: ipodder2003 on June 11, 2004, 09:46:00 PM
Post by: FBF on June 12, 2004, 01:19:00 PM
| QUOTE |
| ldots Posted: Jun 11 2004, 10:22 AM There could very well be updates. Is there something you feel is missing? If you have any ideas, feel free to post them. |
The only thing I can think of is the new Bert_ate_Ernie fonts, with another dash
Great Package btw
Post by: ldots on June 13, 2004, 12:56:00 PM
I'm putting the final touches on a new version that has MXM wrapped around it. You can still use the package as before running the mini-linux, but can also now just select the disired action from a menu :
- Run Mini-linux
- Install UDE
- Uninstall UDE
- Backup
- C-restore
Using these actions, everything is automatic - you only need you controller. I still recommend ftp'ing out the eeprom and hdd-info generated be the installer though.
Will post more when released.
Post by: triggernum5 on June 13, 2004, 01:46:00 PM
Post by: ldots on June 14, 2004, 05:04:00 AM
NOTE. From version 1.3 this package was wrapped in a graphical front-end provided by MXM. The linux toolbox is still available (and unchanged) when running the 'Run-linux' option of this MXM menu. This MXM menu was created to make it easier to install/uninstall UDE without the use of a telnet connection from a PC. The linux toolbox is still very useful though, as many of the tools included are not available from the MXM menu. The description below still applies for the linux toolbox.
For information no the graphical interface look here
Post by: ldots on June 22, 2004, 02:44:00 PM
To go on live you would have to uninstall. Play on live and afterwards reinstall using an exploitable game (007,MA,SC).
Edit : You do know there is a more up to date thread on the new, graphical versions?
Post by: usuariofinal69 on July 02, 2004, 07:04:00 AM
all is fine but when I star my box with the dvd open and go to the Matrix screen and go to the Dashboards and select Xdk it send me to the error screen 21 
the same thing if I try to start a backup from that screen (go to error 21)Someone help me please, what can I do?
Post by: N3LDAN on August 10, 2004, 10:32:00 AM
Post by: sean_2k5 on August 16, 2004, 02:41:00 PM
[email protected]
Post by: sean_2k5 on August 16, 2004, 02:49:00 PM
[email protected]
Post by: Maffers on September 24, 2004, 03:31:00 PM
Post by: Morgentaler on October 15, 2004, 03:43:00 AM
Anyway, now I don't have to deal with the bloody pogopins unseating every time I move my box around the house.
Anyway, great job Idots, and those who pummel him with questions. It's always a learning experience.
Post by: bobthenob on November 29, 2004, 09:32:00 AM
red loads linux menu hope this helps
Post by: Tifer on November 29, 2004, 07:51:00 PM
Post by: bobthenob on December 01, 2004, 12:48:00 AM
Post by: bobthenob on December 01, 2004, 11:28:00 AM
then loaded the game
then loaded the save game from hard drive not memory card
Post by: Tifer on December 03, 2004, 01:59:00 PM