Oct 7 2004, 04:52 PM
Frieko's guide to the Uber XBE Exploit via EvoX gamesave exploit (MA, 007, SC) and FTP
As always, I AM NOT RESPONSIBLE FOR YOUR ACTIONS AS A RESULT OF THIS DOCUMENT! ALL XBOX MODDING RISKS VOIDING YOUR WARRANTY, BANISHMENT FROM XBOX LIVE, OR DESTRUCTION OF YOUR XBOX SYSTEM!
Thanks to pedrospad, rmenhal, devz3ro, angerwound, and others for creating this awesome mod and for helping me install it.
Idots has done some great work with his ltools UDE installer. If your XBOX is compatible, go ahead and grab that off the usual places and use it. However as of writing it doesn't work well with NTSC-J, PAL or new boxen with Xcalibur video encoders. If this is true, or like me you just like to be difficult, never fear, you can still install UXE on your XBOX with a plain old EvoX-loaded gamesave exploit, which is what I will show you now. This operation SHOULD be compatible with all known xbox from version 1.0 - 1.6. I didn't QUITE write a noob guide, but if you've done any modding in the past and you have a reasonable grasp on the lingo, or you're a clever and brave noob, by all means proceed.
You will need:
> A Free-X compatible game (an original disc) and exploit gamesave loaded with EvoX. Currently hacked games are 007 Agent Under Fire, MechAssault, and Splinter Cell. The gamesaves are available on the usual places.
> An ethernet setup from your xbox to a computer with FlashFXP or other FTP client installed.
> Make a note of your Kernel and Dashboard versions. They can be found in the dashboard, at settings->system info.
> Xbox Kernel 3944 4034 4627 4817 5101 5530 5713 or 5838 (pretty much all known kernels)
> Xbox dashboard with an "Xbox Live' tab. Preferably 4920 or higher. You can get D:4920 from Slayer's (you don't need to install it, just grab update.xbe for step 8), or try popping in a game cd and clicking on 'Xbox Live' which should update.
or alternately the command line version s1994752.zip
(1994752 is the magic number for uxe, it comes from the byte size of the .xbe used)
NOTE: A LOT of people including myself have trouble getting uberpatcher to load. I's probably some .net crap, so you can try upgrading your .net but it's probably easier to just use the command line version.
> metoo-m8plus-v1.4.1.zip [usual places]
> EvolutionX dashboard. [It's either in your gamesave, or grab it off the usual places]
> Idot's dashboard font patcher [usual places, xbe-xip-xbx-tools in PC section]WARNING:
If you have to stop in the middle of this operation, you should first use the backup from Step 6 to restore your xbox to factory spec before you walk away. Although this exploit does NOT suffer from the clock bug after it is installed, leaving the xbox without power while it doesn't have a working hard disk boot sequence (custom or original) will cause your xbox to frag.
Quick technical analysis: PedrosPad found a way to font-hack xboxen without risk of the clock bug. Instead of hacking xboxdash.xbe where the clock bug lives, they find another craptacular .xbe file that's free of the bug but still exploitable, name it xboxdash and hack it instead. Very clever. Basically after that you throw some crafty files into the fonts folder and wait for the magic to happen. xboxdash.xbe gets tricked into loading the Phoenix BIOS Loader, which in essence is the software version of a modchip. It injects a new custom BIOS-kernel into the system.
Devz3ro's original thread can be found here.
If you have everything you need, let's begin:Step 1.
Boot up a temporary EvoX dashboard using a game save exploit like 007:AUF, MechAssault, or Splinter Cell
Here's a guide by jsrlepage:
This is how I succeeded in installing a software modification under an Xbox with the Splinter Cell exploit.
What you will need :
- Unmodded, unopened, under extended warranty Xbox :-D (that's mine - no wonder I didn't want to do a machine-open)
- Splinter Cell (Tested with a non-platinium)
- Memory Card (I used a MadCatz. meow.)
- A friend with a modded, or someone who made THAT/a hack and can lend you a card with the Splinter Cell hack/copy the savegame hack to your card.
- Home network (or anything, as long as you can FTP to your Xbox).
- Hack 1 : Splinter Cell Exploit (usual place)
Steps BEFORE exploiting your Xbox
Unpack every archive you downloaded. You should unpack them in different directories, but as subdirectories of the same directory.
Steps to get your savegame on a memory card.
1- Ask a friend to upload them to a clean/without-Splinter-Cell-saves memory Card
1- Ask a friend who has a memory card to copy the savegame to it (backuping his SC saves and deleting them before copying the exploited ones.
Steps AFTER you got a Memory Card with the savegame.
0- Before anything, double and triple-check that your Xbox is accurately plugged (power cord, audio-video output) and plug your Box on your private network.
1- Access your box's current dashboard, go in Memory>Hard Disk and delete any Splinter Cell savegame you currently have - the hack must be the ONLY Splinter Cell savegame present on your Xbox.
2- Still in the original dash, go in your memory card, and copy the two save slots (Linux Installer and the Splinter Cell Savegame) to your hard drive.
3- When you have sucessfully copied the two savegames (the Linux Installer should have a "Debian" logo, and maybe even the Splinter Cell Savegame), insert your "Splinter Cell" game like if you were going to play.
4- Get into the menu, choose "Play", then take the "Linux" profile, and select "Checkpoints" with the "A" or "Start" button of your control pad. Don't worry, there isn't supposed to be any checkpoint entry.
5- BAM! You have sucessfully loaded EvoX! Which means you now have a FTP server. Advice : take down your IP address. You can get it in "System Utils" > "Settings" > "IP" (the first one you see).
In EvoX, go to Settings and make sure the network settings are correct, save and reboot if you have to change anything.Step 3.
Use the EvoX "Backup BIOS and EEPROM" function.Step 4.
Use an FTP client to access your XBOX.Step 5.
Pull the "backup" folder created in step 3 onto your computer for safe keeping. It will be in e:\UDATA, use FTP search if you can't find it.Step 6.
Pull the entire contents of your XBOX's 'C' drive onto a folder on your computer.Step 7.
SWEAR TO ME YOU REALLY DID STEPS 5 AND 6! ;-) You will need them if something goes wrong.Step 8.
Make a new folder on your computer and copy the file c:\xodash\update.xbe from your XBOX into it. (On a side note, update.xbe can also be found in Slayer's.)Step 9.
Run Uberpatcher and select the update.xbe from step 8 and click patch. This will create a file xboxdash.xbe. Alternately, use the appropriate command-line patcher and name the output xboxdash.xbe.Step 10.
Right click on this file, hit properties, and verify that it is 1,994,752 bytes in size.Step 11.
Now the fun begins. Go back to your FTP client, and copy the following files from metoo-m8plus into the root of your E: drive to install the BIOS loader:
Install EvoX dashboard to your xbox C drive. Your game save should have an "Install EvolutionX" tab, otherwise just put an evoxdash.xbe, evox.ini and 'skins' folder into your C. You will probably want to edit evox.ini later, or put your other dash of choice in C: (Just be sure to rename the new dash evoxdash.xbe)Step 13.
In your XBOX C: drive, rename xboxdash.xbe to msdash.xbe. Then take the new uber-patched xboxdash.xbe from Step 9 and put it in the xbox C:Step 14.
Rename the folder c:\fonts to f0nts. (notice the zero) You can leave C:\xbox.xtf and c:\xbox book.xtf alone.
[NOTICE: Steps 15A-15C must be done all at once and in the order I show. The reason for this is that update.xbe must find bert before it finds ernie. Technical details here
, otherwise just trust me. If for any reason you end up with the wrong files, remove the fonts folder and make a new one.]Step 15 A.
Make a fresh new folder on your xbox C: drive called fonts. B.
Copy bert-xxxx-01.xtf (where xxxx is your xbox's original kernel version) from the s1994752 folder of the updatefonts71 package to your xbox C:\fonts folder C.
Copy ernie.xtf from updatefonts71 into c:\fonts
Your xbox directory tree will now look like this:
| +-- Xbox.xtf
| +-- Xbox Book.xtf
| +-- bert-xxxx-01.xtf
| +-- ernie.xtf
+-- msdash.xbe (your original dashboard)
+-- xboxdash.xbe (the exploited .xbe made from update.xbe)
+-- (some other files/folders like audio, xboxdashdata, xodash, xbox.xtf)
+-- default.xbe (metoo BIOS loader, it is signed with the habibi key)
+-- Metoo-M8plus_16-06.bin (metoo looks here by default, otherwise edit boot.cfg)
+-- (maybe some other stuff, shouldn't matter
Step 16. Take out the game DVD and your memcard, power off the xbox and turn it on.
Step 17. Within 15 seconds you will be looking at one of two things:
|Thing A: The EvolutionX dashboard. If so, congrats! The exploit is installed. You will want to edit your msdash.xbe to get your original dashboard working again. Put Idot's patcher.exe and your original msdash.xbe in a folder together. Go to cmd prompt, change dir to your folder, and run the patcher. For example if your files are in c:\patcher, type:|
patcher msdash.xbe -f0nts
Then name the output file msdash.xbe and put it in xbox C. Call it from Evox or other dash and it will access the f0nts folder and load as the regular MS dash. From evox.ini that looks like:
That's it, install your apps and enjoy
|Thing B: The X screen, nothing, a greenish screen, or something, but whatever it is it's frozen or otherwise not Thing A. If so, reinsert the exploited game CD and go back to EvoX, a la Step 1.|
Skip to Step 15, but with one of the following changes:
Try adding the s.xtf file to c:\fonts
Try using bert-generic instead of bert-xxxx
Remember to delete the fonts folder and make a fresh one.
Try using the updatefonts61 package instead of 71.
Try UDE1 or UDE2 instead, if they are supported by your xbox type.
If you still haven't succesfully booted, restore your xboxdash.xbe and normal fonts folder using your backup copies from Step 6. Your xbox should boot into MSDash normally. Reread this tutorial, browse the forums, get help.
Some extra customization notes:
*The M8plus bios boot order is DVD, evoxdash.xbe, avadash.xbe, nexgen.xbe
*M8plus supports large hard drives via LBA48 and F:
*If you don't like M8, m8plus can be used to load any BFM bios simply by changing the Romfile line of the boot.cfg file. No need to change the RC4 keys or anything. Other bios are available in /XBOX/bios/bootable from media/hacked/ in usual places. I tested this with X2_4983_BFM.rar and it worked fine for me.
Good luck and happy modding!
Oct 7 2004, 06:11 PM
Please dont take this as an insult as its not meant to be but this could be exactly what we need until ldots releases his package.
Its great to see more people willing to share their knowledge/experience.
Oct 7 2004, 08:50 PM
Does the m8pack look for those specific bios file names or did you forget to make sure they are named 'xboxrom.bin'?
Oct 7 2004, 09:10 PM
yeah i kinda wrote it for two reasons, for people that can't wait for idots, and people that like to know exactly what their auto-installer is doing inside their xbox.
when a New Modding Thing comes along, i tend to just throw all the files into my existing xbox toolkit and add an evox script rather than have a bunch of different installers for everything. just a matter of personal preference. so admittedly i kinda wrote this for myself as much as i did for you guys...
Oct 7 2004, 09:15 PM
|QUOTE (Angerwound @ Oct 7 2004, 09:53 PM)|
| Does the m8pack look for those specific bios file names or did you forget to make sure they are named 'xboxrom.bin'? |
i believe it already points to one or the other. i dont remember which and i'm not at home so i cant look. but so far i've just gotten away with unzipping the package right into E:
i'll verify tonight and post back if i'm wrong
Oct 7 2004, 10:13 PM
So, I don't have to delete the xbox book.xtf xbox.xtf that are in the root of c:? I remember that was important and needed before.
Oct 7 2004, 10:35 PM
|QUOTE (Angerwound @ Oct 7 2004, 09:53 PM)|
| Does the m8pack look for those specific bios file names or did you forget to make sure they are named 'xboxrom.bin'? |
I just checked the code and it looks for M8_LBA48_IGR_Q-06-BFM.bin. But I can't see why you should install both, except it goes faster to change.
Oct 8 2004, 12:47 AM
|QUOTE (gronne @ Oct 7 2004, 11:16 PM)|
| So, I don't have to delete the xbox book.xtf xbox.xtf that are in the root of c:? I remember that was important and needed before. |
d'oh! yes, still need to. knew i forgot something. well thats why i asked for comments, thank you.
well the short answer to your other question is it doesn't hurt to have both.
Oct 8 2004, 01:19 AM
Yep you can leave the ones in the root. The update.xbe used in UXE and checks the fonts folder first.
Oct 8 2004, 12:22 PM
Aren't your answers contradictionary? To me I seems like Frieko says you still have to delete them. And Angerwound says you can leave them as is. Sounds like Angerwound knows the technical process of UXE, so I guess I'll just leave them.
Oct 8 2004, 12:44 PM
|QUOTE (gronne @ Oct 8 2004, 01:25 PM)|
| Aren't your answers contradictionary? To me I seems like Frieko says you still have to delete them. And Angerwound says you can leave them as is. |
The update.xbes used for UDE1/UDE2/UXE check the C:\fonts folder first, and if it can't find the fonts it's looking for, it then checks C:\ root.
So as long as all the necessary fonts are in c:\fonts, C:\ root isn't checked!, so leaving the legacy pre-live Dashboard fonts there is harmless.
Oct 8 2004, 02:25 PM
yeah sorry about the confusion, gronne. you can leave them alone.
Oct 8 2004, 06:42 PM
I installed UXE. And it's working better than I thought. I don't know if it's got to do with the bios or not, but now I can do IGR in evox. Saves me a lot of time when the ftp-connection gets stuck. Really sweet.
ADD: Everyone probably understand it, but nr.14 should be that you shall upload the patched xboxdash.xbe to the box. I fortunately discovered I hadn't uploaded it before I restarted my box, but someone might not.
Oct 8 2004, 07:15 PM
fixed, i put it in step 13 so i didnt have to renumber everything haha
yeah it's prolly that sweet sweet M8 bios hookin you up.
Oct 8 2004, 11:00 PM
|QUOTE (frieko @ Oct 8 2004, 08:18 PM)|
| fixed, i put it in step 13 so i didnt have to renumber everything haha|
yeah it's prolly that sweet sweet M8 bios hookin you up.
Now this guide is looking good. "Unfortunately" no one will need to use it when Ldots release his program. But still, the most thorough guide so far.
Oct 11 2004, 05:15 PM
Have used this guide to do my 7th box now and it roxx like he*l
One thing thats missing IMAO is how to get MSdash work, well there's other topics about that
but the guide whould more "complete" with it..
anyway thx for a superb guide
Oct 11 2004, 07:06 PM
you're welcome, glad you found it useful. sounds like you figured it out already, but anyway you get the ms dashboard f0nts patcher off usual places and tell it to wash your original dashboard xbe like so:
patcher msdash.xbe -f0nts
take the new file, name it msdash.xbe and throw it in c:\
i'll edit the article eventually
Oct 12 2004, 12:10 AM
thank u guys for this great tut...its great to see how fast and simple it could be=)
Oct 12 2004, 10:18 AM
Great tutorial. Going to use it for the new Chrystal PAL editions that will be available over here soon.
Oct 12 2004, 07:10 PM
U people ARE great...!
Thanks to Pedros for his continued effords on xonline!!!
Oct 12 2004, 11:18 PM
i just want to make sure that im not going to get any error msg with a 1.6 box. ive been reading about the font hack and from what i read is that some games like amped or others can overwrite the fonts to original. upon reboot you will get a error msg. I DO THANK YOU FOR THIS GREAT TUTORIAL BUT I JUST WANT TO MAKE SURE THAT I WONT HAVE PROBS ON A 1.6. its a friends box and i dont want to frag his box.
thanks any replies would be appreciated
Oct 13 2004, 07:58 PM
Nice tutorial but is there an error in step 5? was'nt the back-up created in step 3
"Step 5. Pull the "backup" folder created in step 2 onto your computer for safe keeping. It will be in e:\UDATA, use FTP search if you can't find it".
I am a noob but with a little knowledge "which is dangerous" could somebody explain why i need to use the Dasboard Font Patcher.
I think it makes my M$dash still usable but can i choose from either of them to boot after the patch, if so how?
sorry for my total lack of understanding but i only got my xbox yesterday which is v1.6 pal so i cannot use ltools well not version 1.7.5 & i only have 007 & SC so RC1 1.8.0 is'nt an option.
Could someone spare a little time to help a noob who cannot wait for the new ltool packages.
Updated: does'nt matter i got mechassault & installed rc1 1.8.0 "not like anyone was going to reply anyway, no wonder theres so many noobs with no-one helping"
but its a dog eat dog world so sh*t happens
Oct 14 2004, 12:16 AM
TNX Frieko a very full and clear guide. I wil try all your words in few days.
Wait my comments!
Oct 17 2004, 10:01 AM
I tried using this method after other UDE1/2 methods failed for me but I'm already running into trouble with this before even transferring files to my box.
My update.xbe is 2,260,992 bytes but uberpatcher won't patch it. The patcher itself just hangs when it loads up, showing just a Team O2X.info splash screen. if I use the command line version it tells me the file can't be patched because of an unexpected checksum. It does this on both the update.xbe from my unmodded box as well as the one from Slayers 2.6.
My Xbox is Kernel 4034 with Dash 5960.
Oct 18 2004, 02:05 AM
|My update.xbe is 2,260,992 bytes but uberpatcher won't patch it.|
i actually had uberpatcher hang like that on my computer, but nobody else has complained so i thought it was just me. *looks sheepish* im running xp home, how about you?
to use the command line version, rename your update.xbe to s2260992.xbe then put it in the same folder as s2260992-s1994752.exe and run that exe. preferably from a command line so that you can see the output. if that doesnt work then maybe your xbe or exe is corrupt.
by the way, what region are you? if you're north america ntsc then you should be able to use ltools to install ude2 on a 4034. what kind of trouble were you having?
Oct 18 2004, 02:28 AM
|from what i read is that some games like amped or others can overwrite the fonts to original. |
i honestly don't know. i haven't heard of that but that doesn't mean it's not possible. ms is always doing retarded shit to a-splode our boxen. its up to us to stay one step ahead of 'em.
in any case, if something does frag uxe, you can still boot with the game-hack and uninstall it provided you have the original c: contents backed up. just do it quick, i believe if the power goes out while your c: is hosed you can get a clock loop.
if you've done evox scripting before, you could edit the gamesave's evox.ini and add something like this to automate the process. (this is just a quick template to show you what im talking about, if you're unsure what i mean just ignore it.) :
Info "Restore Factory C:"
Warning "Un-Mod XBOX?"
copy "e:\cbackup\" "c:\"
in conclusion, im not gonna make this call, it's up to you. maybe somebody else can give you more definitive answers.
Oct 18 2004, 02:41 AM
|Updated: does'nt matter i got mechassault & installed rc1 1.8.0 "not like anyone was going to reply anyway, no wonder theres so many noobs with no-one helping"|
point a, im not sure what people dont understand about the font patcher, you just run it on your original xboxdash.xbe, name the output something (wonkydash.xbe, supermariobros.xbe, pooponastick.xbe it really doesnt matter) and throw it in xbox c drive. when you run it you will get regular dash.
point b, sorry i didnt reply, i just got gmail and the topic notification musta fell thru the cracks in the switch. congrats for getting along ok on your own.
Oct 18 2004, 11:35 AM
...However as of writing it doesn't work well with NTSC-J, PAL or new boxen with Xcalibur video encoders...
Only want to tell:
I tried it on XBox PAL, 1.6 (with Xcalibur), K:5838 D:5960 and it worked well. No problems so far.
Thanks for the great tutorial!!
Oct 21 2004, 06:24 PM
i can't find the uberpatcher in the usual places. if someone could help out a little i would be forever in their debt
scratch that, i think i owe everyone who read my post an appology. so i'm sorry.
Oct 21 2004, 09:14 PM
|QUOTE (rabitoedan @ Oct 21 2004, 07:27 PM)|
| scratch that, i think i owe everyone who read my post an appology. so i'm sorry. |
haha apology accepted
Oct 23 2004, 09:59 PM
Okay.. well everything went great! Until step 15a. A folder called f0nts had already been created (unmodded system) and when I inserted the new fonts folder everything stopped. Now I just get the green screen of death and no boot. I am stuck at this point. The exploited game won't start. Any ideas?
I am glad to have had a modded system for a few minute
Oct 24 2004, 09:37 AM
Thanks for this GREAT tutorial!
I softmodded my first Xbox this morning following your tut and it worked great at first try!
Oct 24 2004, 12:48 PM
I can't get this UXE exploit to work on a 1.6 PAL XBox. I'm sure i made all the correct steps to install UXE, but before switching to more powerfull methods I still like to now why this Xbox refuses to be exploited.
First things first, this is what I did sofar:
- Got a new 1.6 PAL Xbox, and a 160GB Maxtor HDD
- Found out it had K:5383 and D:5969
- Used memcard with SC Exploit and SplinterCell CD to boot into Evox
- Did a full backup of C: and E: to my workstation
- Used xboxhdm to re-build the new HDD with the contents of the original HDD
- Locked HDD using xboxhdm and eeprom.bin dump from Evox
- Re-installed new HDD
So far, so good. The box runs fine on the new HDD. Now on to installing UXE:
First I got update.xbe from C:\xodash. I patched it using s2387968-s1994752.exe (File was 2387968 bytes, in my case). Renamed C:\fonts to f0nts and put the new bert and ernie fonts in it (in that particular order). XBox kernel version is 5838 (verified by both M$ 'About' screen and Evox), so i used bert-5838-01.xtf.
I uploaded and configured metoo-m8pack-v1.2 and Evox V3935 for UXE to boot into.
This should be enough to have softmodded this XBox, I thought. When i removed the SC DVD and cold booted the box it showed the nice 'Maintainance required' screen with Error code 21. Since then i've been trying various things and still haven't been able to fix this error. Sometimes I got Error 13, but I guess thats what you get when not all Dashboard files are OK.
What i've tried so far:
- Restoring the original HDD (working) contents, upgrading the Dash using XBox Live! console and installing UXE again.
- Using lots of different bert.xtf, and s.xtf's.
- Booting into a Font-signed Evox instead of PBL (default.xbe replacement)
- Used uberpatcher.exe instead of command line patcher
I can't figure out whats causing these errors. I've modded 30+ xbox's, from version 1.0 and up. This is my 1st UXE install though.
Can somebody tell me what i am doing wrong, before I revert to UDE2? Since its a PAL xbox, it has to be region changed first, and thats not the prefered method here
Oct 24 2004, 07:18 PM
excellent tutorial frieko. got uxe up and running smooth on a 5713 box.
Oct 25 2004, 06:47 PM
|QUOTE (mwvw @ Oct 23 2004, 11:02 PM)|
| Now I just get the green screen of death and no boot. I am stuck at this point. The exploited game won't start. |
you should be able to hot swap either to a modded xbox or a pc with xlinux or comparable (i've never used xboxhdm, is is useful for this purpose?) and restore your original config.
as to why it didnt work in the first place, was the xbox is completely stock, or was it previously modded?
Oct 26 2004, 09:51 AM
I have a question:
I modded my xbox following this tut and everything it's ok, but I can't access the original MS Dashboard. If I unplug the power chord, how con I reset the clock on the Xbox ?
Oct 26 2004, 04:18 PM
|QUOTE (Fox1983 @ Oct 26 2004, 10:54 AM)|
| I modded my xbox following this tut and everything it's ok, but I can't access the original MS Dashboard. If I unplug the power chord, how con I reset the clock on the Xbox ? |
okay i just made a fresh, detailed, free of the lame leetspeak joke, Step 17.
RRTFA (re read the frieko's article)
Oct 26 2004, 04:30 PM
|QUOTE (JJay @ Oct 24 2004, 01:51 PM)|
| I can't get this UXE exploit to work on a 1.6 PAL XBox. I'm sure i made all the correct steps to install UXE, but before switching to more powerfull methods I still like to now why this Xbox refuses to be exploited. |
no clue, sorry. didn't spot any errors in your report.
out of curiosity, did you try with the original harddrive?
Oct 26 2004, 06:18 PM
I am thinking of exploiting a 1.6 crystal Pal Xbox but I really dont want to fuck the Xbox up.
(Call me chicken shit but i don't have a job or anything and £100/$200 is a lot to me!)
So can someone tell me what the worst case scenario would be and how it would be fixed?
Oct 26 2004, 06:51 PM
|QUOTE (frieko @ Oct 26 2004, 05:21 PM)|
| okay i just made a fresh, detailed, free of the lame leetspeak joke, Step 17.|
RRTFA (re read the frieko's article)
Thank you very much!
That solved my problem!
Oct 26 2004, 08:09 PM
followed the guide and it was the first one to work so thanx for that
are you ment to be able to put `backup`
Discs in and be able to play them. i put one in on Evo X and it just stays on `in` (goes of the screen) and just sits their, have i done anything wrong or are you not ment to be able to play `backups`?
thanx for any help in advance
Oct 26 2004, 09:27 PM
|QUOTE (ZAP @ Oct 26 2004, 07:21 PM)|
| I am thinking of exploiting a 1.6 crystal Pal Xbox... So can someone tell me what the worst case scenario would be and how it would be fixed? |
worst case scenario is that you get arrested, your house burns down, your mom is featured in the latest paris hilton video, and you develop a crush on tony blair.
okay the two main disaster scenarios are
1) you get banned from live, which is (sometimes) fixable by writing in an unbanned eeprom.
2) you are unable to boot your xbox at all. but the nice thing about soft-modding is that there is no chance of physical damage to the box. however if you are unable to restore your original software via the gamesave, you will have to open the box and hot-swap. not sure about your local laws but here that voids your warranty.
as always, make sure you backup your harddisk and EEPROM!
Oct 26 2004, 11:10 PM
lol, thanks frieko
Well is it really possible though that it will fuck up and not boot up? Or is that black/green screen of death thing pretty much the only shit thing to happen if i follow the steps?
I dont't intend to play on Live so that is not really an issue.
Oct 27 2004, 02:46 AM
|QUOTE (ZAP @ Oct 27 2004, 12:13 AM)|
| Well is it really possible though that it will fuck up and not boot up? Or is that black/green screen of death thing pretty much the only shit thing to happen if i follow the steps? |
correct, the kernel will still boot and "flubber" no matter what.
Oct 27 2004, 06:35 AM
Ahh so if i were to mess up, i would still be able to fix it without having to open the box up yeh?
Thats one of the best things about the exploit because it won't void warranty
Oct 27 2004, 02:27 PM
|QUOTE (ZAP @ Oct 27 2004, 07:38 AM)|
| Ahh so if i were to mess up, i would still be able to fix it without having to open the box up yeh? |
i would never make a guarantee.
but yes, barring rare circumstances it does seem to be a safe, reversible operation.
Oct 28 2004, 10:02 AM
Just wanted to say thanks Frieko for the tutorial - the instructions are good & worked a treat on my Pal xbox K5101, D5659
This post should be pinned until Ltools1.8 final is released.
Oct 28 2004, 03:07 PM
any one know why i cant play `backups`?
Oct 28 2004, 03:41 PM
im writing a little (linux) script to simpify this process, but i got 2 questions, just to make sure i dont screw
1. does Evox always save the eeprom backup in the same folder?
2. is there a linux alternative for Uberpatcher?
as for question 2: can i just use an already patched update.xbe on any other xbox? i've tried this already
and it worked fine, but i cant be sure if i was just lucky(eventho the original update.xbe was from a 1.6 xbox
and i used it to softmod a 1.0 xbox, on which i couldn't even find an update.xbe)
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here