Jan 15 2004, 09:45 PM
okay i had the bert and ernie reloaded installed restarted xbox and evox booted up problem is when i insert a game or try to do something it comes up with error 21 i have no idea what's wrong and i'm am still quite new to this. my xbox is K: 5101 D: 4920 any help is appreciated. (i uninstalled it now since it didn't work but i can always re-do it and i DID make back-ups of hard drive so i should be okay if i mess up) by the way, i've heard something about the pheonix bios loader or something? would that help? plz let me know
Jan 15 2004, 11:59 PM
can any 1 please try and help me out?
Jan 16 2004, 03:18 AM
Email me firstname.lastname@example.org.
PBL changes the bios that are loader (not permantly just loads it and plays it while on and loaded lol)
Jan 16 2004, 04:13 AM
If you're getting into EvoX, you've already made a big step in "softmodding". Technically, you can already play backups and homebrew apps. The only catch is that with your current setup, you need to sign every XBE file you want to run. The program that will resign XBE's is called xbedump. Because you're using the font exploit, you need to use xbedump to sign every XBE you want to run with the font signature.
|xbedump default.xbe -font|
In the example above, I'm trying to resign the file default.xbe with the font signature (notice the -font). xbedump will create a new xbe file called "out.xbe" that is a font signed version of the original "default.xbe". Rename/disgard the original default.xbe so you don't confuse it with the new signed version, then rename "out.xbe" to "default.xbe".
If you want to try go above and beyond your current setup, PBL is the way to go (as far as software modification goes). I'm guessing your current setup looks somewhat like is this:
C:\evox.ini (optional file; EvolutionX configuration)
C:\Skin (optional folder; EvoX Skin folder)
By optional, I mean you may or may not have these files. They're good to have in terms of customizing, but not vital for EvoX to run.
The fonts are designed to launch the file C:\default.xbe, which in your case is a font-signed EvolutionX dash. There are several ways to implement PBL with your setup. 1) as a seperate app, or 2) making it autoload first.
Most people chose the 2nd option as it unlocks your XBOX immediately before EvolutionX boots, thereby allowing you to run unsigned software without any problems.
To do this, you need to either obtain a font-signed copy of PBL or just download PBL and use xbedump to font sign it using the method explained above. I'd recommend getting PBL 1.3.5 as it allows you to switch between BFM BIOSes. Anyway, after you've acquired PBL 1.3.5, you need to setup the boot.cfg file. It requires a debug RC4 key and two EEPROM keys; those you'll have to find on your own at the "usual places", as I won't tell you them. You'll also need to acquire at least one BFM BIOS. Try out the X2 4979.67 BFM BIOS first, then you can look for more later. Make sure it's a BFM BIOS (the filename will have "BFM") or else PBL will hang shortly after loading. After you have the bios file (for example, 4979.67_bfm_256k.bin), rename it to xboxrom.bin and move it to PBL's Bioses folder.
After that is done, you'll need to do some rearranging. Remember how I said that the font exploits load C:\default.xbe? Right now, your EvolutionX dash is named default.xbe. *Rename it to evoxdash.xbe. Then, copy all the files for PBL to your C partition. You should end up with these files:
|C:\default.xbe (PBL 1.3.5 XBE)|
C:\evoxdash.xbe (Evox dash that was originally named default.xbe)*
C:\evox.ini (optional file; EvolutionX configuration)
C:\Skin (optional folder; EvoX Skin folder)
What happens is when you boot up your XBOX, the fonts load, causing C:\default.xbe to run. C:\default.xbe is PBL which loads the bios file C:\Bioses\xboxrom.bin. The BIOS file (unless it was modified) is designed to look for C:\evoxdash.xbe.
That's a quick overview of what you need to do. I'll try monitor this thread when I have free time (when being the keyword <sigh>), so if you have any questions or get stuck, post the question. Either I or another nice person on X-S will help you out.
PS. Quick overview of files you'll need: PBL 1.3.5, a BFM BIOS (X2 4979.67 BFM or equivalent), xbedump (if you need to sign XBE files), and you'll need to find the RC4 and EEPROM keys for the boot.cfg.
EDIT: You could upgrade your evox dash during this process, but I figure you can do that after you get this up and running.
Jan 16 2004, 11:28 AM
thank you i'll try this out and see what happens.
EDIT: ok there is 1 problem i looked at my "usual places" and i couldn't find rc4 key, but i did find the eeprom and bios
i'm, going to keep looking but i'm not comint up with any thing i'll let u know if i find it....
Jan 16 2004, 07:19 PM
OK i used the signed PBL and then when i started up my Xbox it had a scrolling screen. I don't know what i did wrong....
Jan 16 2004, 09:22 PM
What sort of text does your "scrolling screen" have? I know if you use a regular BIOS file, it will display some text, an RC4 key (if I remember correctly), then freeze. Make sure the BIOS you're using is a BFM BIOS file.
If it says:
Loading ROM: P:\Bioses\xboxrom.bin
Error opening bios file
Application died in an unhappy manor. Press A to reboot.
Then, you're either 1) missing a BIOS file in your Bioses folder, 2) The BIOS file set to autoload in the boot.cfg doesn't match the name of BIOS file that you have in the Bioses folder.
A description of the text might help, then I can try look into it.
Jan 16 2004, 09:40 PM
the signed version didn't have a bios folder i just pasted everything in there the screen scrollled and i could see that evox loaded, but it was hard to see since the screen was scrolling so fast... could it be that i have a newer xbox? mayb the signed one wasn't using x2 casu i read the file and it said it supported my xbox or the evox is older.... hmmm also why i used the signed version is becaus i couldn't find the RC4 key.
Jan 16 2004, 09:50 PM
The version of your XBOX looks okay; I know people with those specs that have gotten it to work.
The tutorial I gave was based on the idea that you'd be using PBL 1.3.5. If you don't have a "Bioses" folder, you're probably using an older version, perhaps 1.3. In that case, the BIOS goes in the same folder as PBL so your layout would look like this:
Do those files match the files in the package you're using? Also, you can simply open boot.cfg with a text editor and copy-paste the RC4 and EEPROM keys from the signed one to the newer PBL 1.3.5 and resign the XBE file in the PBL 1.3.5 package.
NOTE: If your RC4 keys and EEPROM keys consist of all 00's (0X00 0X00 ... 0X00), those are default invalid keys... you need to find the right keys.
Let me know if the files above are the ones you have so I know which version you're using. If your files match what I originally stated, it should have had a Bioses folder... if not make a folder named Bioses and move the xboxrom.bin file in there.
EDIT: BTW, the X2 4979 BFM BIOSes won't work with PBL 1.3 (forgot to mention that), if you really must use PBL 1.3, get the 4977 BIOS
Jan 16 2004, 10:57 PM
yes i was using signed PBL 1.3 caus that's the newest 1 they have and it came with bios... i think it's too old tho caus my xbox has a newer video thing or somethin as i've heard about so i will have to go with the newer PBL and edit everything that seems like the best way to go for me right now.
Jan 16 2004, 11:27 PM
Yeah, the newer Focus encoder causes a lot of headaches when people try to softmod (when using older versions of PBL), which is why I always end up recommending using PBL 1.3.5... saves people the trouble of thinking it was their configuration that was wrong, when it was simply the software.
As a little sidenote, when signing with xbedump, use the command I gave earlier. What will happen is that xbedump will create a new xbe file called "out.xbe" that is a font signed version of the original "default.xbe". Rename/disgard the original default.xbe so you don't confuse it with the new signed version, then rename out.xbe to "default.xbe". I figure I should mention this so if you run into Error 21's and all the files are laid out correctly, this is the culprit.
PS. I will update the original walkthrough to reflect this note.
Jan 17 2004, 12:16 AM
First off i want to thank you for all your help..
secondly, is PBL 1.3.5i good? i was just wondering as it's not the exact name taht u recommended, but that's the version im' going to try...
Jan 17 2004, 12:23 AM
Ah, no problem, and yes, 1.3.5i will work just fine.
Jan 17 2004, 01:25 AM
OK everything seems alright it loads pheonix bios loader then goes to evox but the run DVD game is red and i can't select it.!?!?!??! some good news tho i can boot up apps and it's no longer error 21
one other thing the light flashes red at start up is this bad?
Jan 17 2004, 01:44 AM
The "DVD Game" being red might have to do with the way your evox.ini is set up. Try opening the evox.ini with a text editor and scroll down to the "[Menu]" part.
If you have a line similar to this:
|Item "Launch DVD", "D:\default.xbe"|
then that's your problem. Try replacing it with this:
|Item "Launch DVD",ID_Launch_DVD|
As for the flashing red, I think that might have to do with the fonts you're using. If I remember correctly, each font was design to set the LEDs to different colors... (I tried the reloaded on mine before I wrote up the guide, and mine also blinked red). You might be able to change the LED color firing in the boot.cfg by setting the LEDSequence to all g's...
I haven't tried this, so I can't say if it'll work, but I found this article which might also be helpful. You're basically hex-editting the fonts to change the LED sequence firing.
The flashing isn't bad, but it can get annoying
Jan 17 2004, 01:47 AM
i think i'll just ignore it it's a lot easier that way
maybe throw a peice of paper over it or something
Jan 17 2004, 01:54 AM
Hmm, never thought of that... I guess that's another fix to the red flashing,
PS. Now that you got this working, if you really want to get rid of the flashing (if the PBL thing doesn't work, and you don't want to hex-edit the font file), you could try using a different font set. Unless they've been modified, they should look for the same C:\default.xbe file; so you could keep a backup of your reloaded fonts, then try out the bigfonts25, for example. If things go awry, just put back your reloaded ones
Jan 17 2004, 01:57 AM
okay now since i edited the file the "run DVD" has dissapeared
maybe i could get another evox ini or something?
i am starting to become very happy that i've finally gotten this far in softmodding!
Jan 17 2004, 02:09 AM
Ah, hmm... what version of EvoX are you currently loading? The reason that it disappeared might have something to do with using an old version of EvoX. The line I gave you was designed for EvoX versions 3752 and above. I can't remember off-hand what the older line would be, so I'll just get you to try and upgrade the dash.
Try finding the newest version EvoX Build 3935 and using the evoxdash.xbe and evox.ini in that package. After you get that up and running, you'll probably have to go back and do some re-editting of your evox.ini to suit your liking though. If you need help doing that, here's a link to a evox.ini guidehttp://xbox-scene.com/articles/evox-ini.php
PS. If I can find the old command, I'll edit this post, but you're probably better off using the newest EvoX DashEDIT
: Ah... um, or you go with the easier solution in looking for a typo... lol (Didn't think of that one <slap forehead>)EDIT: EDIT:
Hmm... what kinda of noises are we talking about?
Jan 17 2004, 02:11 AM
well that was my fault i looked at the newer evox ini and i had the things in " marks so now it works
btw, would u happen to know why it loads these noises when the game save hack is on HDD caus if i remove it it goes back to norm..... Yea lol it was a typo
next i think i will be linking evox to MS dash
Jan 17 2004, 02:24 AM
Hmm, as I said in my EDIT: EDIT, what sorta noises are we talking about? Birds chirping.... chickens klucking...
If you're going to link your EvoX to your MS Dash, you'll need to do some hex-editting for that. As it stands, if you try linking it now, it'll boot into MS Dash... which will load the fonts... err, which will restart the whole cycle if I'm not mistaken... there's a guide to doing this floating on X-S as well as on other forums, so you could look into that. If you can't find it, just let me know. I can run you through it, as it's not too difficult.
: I'm not really sure why that happens...
gamesave isn't that big so I can't see from a technical aspect how it could cause your HD to work harder (if let's say your HD became more fragmented). I never ran into a situation like that, but if you say taking the gamesave off works... I guess you could do that; but it sorta closes that extra window (before hotswapping) if things go wrong.EDIT
: Hmm... interesting... well, I guess you'll be fine removing the gamesave (copy it to a mem card or make a backup of it first), then restoring it before you decide to do anything adventurous with your HD
Jan 17 2004, 02:26 AM
it's more like the xbox vibrates, dunno why.
EDIT: i dunno it only does it when i boot up a game
EDIT EDIT : btw, i forgot to mention i was using th audio exploit and it didn't do it when i got into mxm, but mxm seemed to work good for ftp so i used it, and yea i would deff put it back on if i tried n e thing like what i just did. but i can still boot mxm from evox and delete the save. Might link MS thing to xbox later right now i'm going to explore the wonderful world of xbox apps
Jan 17 2004, 02:46 AM
Ah neato. If you ever need help on the msdash linking, either PM or bump this thread, and I can help you with that. Like I said though, there's a bunch of guides on how to do this floating around. I'll edit this post and add links if I happen to come across em again.
: Here's a few tutorials on how to relink the MSDash in EvoX (when using the font exploit)http://forums.xbox-scene.com/index.php?act...ST&f=45&t=74036http://forums.xbox-scene.com/index.php?act...ST&f=45&t=84734
Make sure when you decided to try and hexedit the MSDash, you hexedit a COPY
of the xboxdash.xbe. Then when you transfer it over to your HD, DO NOT
, I repeat, DO NOT
overwrite your original xboxdash.xbe. If you do, you'll get an error upon bootup. If you're unable to load a gamesave and boot into EvoX, you might have to resort to hotswapping to getting it back up and running.
Rename the hex-editted one to something you'll remember (xftdash.xbe or newdash.xbe, example), then copy it over to your C partition. In the EvoX.ini link the MSDashboard line to your newly hacked dash xbe. (Since you're using PBL, ignore the font signing part)
Jan 17 2004, 02:48 AM
EDIT: btw, i think i figured out the vibrating it was just becaus the disc was scratched or something.... or dirty... wasn't hard drive it was the DVD drive.,,,
EDIT:EDIT: I forgot to say THANK YOU for the whole walkthrough i probably would still be stuck....
Jan 18 2004, 11:19 PM
Wow, this is an awesome thread. Took all my problems and fixed them perfectly... Zogger, thanks for all the help.
Jan 18 2004, 11:40 PM
Ah, heh good to hear that strife. Yeah, we ran into the usual glitches that come up with using the font exploit [and PBL] (thankfully one by one)
Out of all the posts though, I have to commend s0uthp4rk on his creative solution to the blinking LED
Jan 19 2004, 02:48 PM
Does this mean that I can't play burned backup copies of my games when using the soft mod method as described by Mad_Gouki's Xbox Tutorials
How am I supposed to sign the xbes off my backup disc with his method.
I am limited to this softmod technique as my xbox has the 5330 kernel, which is incompatible with pbl1.3.5
Thanking all in advance. Regards.
Jan 19 2004, 03:22 PM
Unfortunately, you're going to have to sign all the XBE's you want to run. The only other program that comes to mind for loading unsigned code (that I can think off), is Complex Loader, BUT that only works with the 4034 kernel (or so the nfo says).
There are several ways to get around this... if you've already made your backup and burned it onto a DVD, you're kinda stuck; you'll have to first rip the files to your HD then copy the XBEs over and use xbedump to resign them. But then you can only play the games off your HD.
If let's say you wanted to make a Slayer's CD that works though, after you get the ISO you can unpack the files with a tool such as xdfsextract, sign the XBE's, then repack it with Craxtion, XISO, or some comparable XBOX ISO maker.
Jan 20 2004, 01:53 AM
I've since resigned to the fate that I will be unable to do a soft-mod as I am running on a 5330 kernel.
I am however, going to run evox without PBL. This however would require me to sign my xbes.
My query is, is there any tools that would allow me to extract my games off disc, and onto the xbox hdd? (I'll then sign the game on the hdd and use evox to load it.)
Jan 21 2004, 05:59 AM
There are various programs out there that can do the job. A couple that come to mind are DVD2xbox and Complex Tools 1.6. They can pull the files off your original DVD, backing up the files onto your hard drive. During this process, they can patch the XBE's to remove any media checks allowing you to run them off the HD. While they can patch XBE's to remove the media check, you will still need to sign them with xbedump.
Jan 22 2004, 04:57 PM
Ok some questions from me, I read this thread over but my questions are now that I have everything working but does the bfm bios have to be renamed to xboxrom.bin? (I'm using pbl 1.3.5 as an app not during startup but i also have pbl 1.3 as my startup along with the font and evox) and if i were to sign the xbe that comes out of a game will i be able to burn it with say nero and have pbl go with x2 bios will i be able to play that game? (not from the hdd but from a dvd r/rw or whatever)
And if not then what does the bios even do? (the bfm bios)
Jan 22 2004, 05:02 PM
Let's see... one question at a time, heh.
You can actually have your BIOS name as it's stock name (X2_4979.06_BFM_BIOS.bin for example), BUT make sure the name in your boot.cfg matches (if you want it to autoload that BIOS that is). PBL 1.3.5i was designed so you can either let the program autoload a BIOS or select a custom one on boot up. This means you can throw as many BFM BIOS files as you want in the Bioses folder, but you need to make sure that you have at least one that matches up with the "Romfile" statement in your boot.cfg or else when it tries to autoload the BIOS, your program will exit with a "unhappy manor" error msg.
If you got PBL and the BFM Bios up and running, I should point out that you don't need to sign anything anymore.
This in a way answers your other question (if I'm interpreting it correctly), that you can make a backup and burn it to a DVD-R (or other medias depending if your drive can read them) then after booting into PBL -> EvoX, play them off the disc. If you have PBL up and running, you don't need to resign any more XBEs. The BFM Bios removes any signature, media, and other security checks, thereby making it unecessary to sign your games.
EDIT: I should point out for others that are reading that if you can't get PBL up (5530 kernel users), you can still sign the XBE before you burn it to a disc.
EDIT: EDIT: Made more edits to try and make the statements more straightfoward.
Jan 24 2004, 01:52 PM
i'm pretty sure that the BFM bios replaces the M$ bios at start up but not permently, as u can just remove everything and it will go back to norm. basically the bios make it so u can run unsigned code on the Xbox with out signing the Xbe's i'm starting to understand the Xbox a bit more now... maybe upgrade from a newbie to a n00b lol, any way sorry i haven't been staying up to date with this thread as it didn't seem like any 1 else was posting
not sure if zogger explained this to you or not.... i didn't quite try to understand whatt he said, and yea no one ever would think of putting a peice of paper over the blinking lite lol
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here