View Full Version : PBL 1.35 & Evox M7 help needed
ParisDragon
01-13-2004, 02:37 AM
I have tried everything the normal way to get the Evox M7ef bios to work on PBL 1.35 with no luck, loads, then screen blanks. I have tried everything I can think of in XBTOOL to fix it. Basically I download M7, set XBTOOL as multi and load the bin. With the proper keys in RC4 in the inis I then switch it to debug, set my BFM flag, change my dash path and save. Then I tried the other debug with 2bl and even BFM.ini, all do the same thing, it loads Phoenix fine, then goes to a blank screen after uncompressing the rom.
I am using an XBOX v1.0 with the 4034 kernal, other 007 load hacks all work fine but I want this combo so I can actually backup from DVDs without a chip, heard this works.
any help appreciated.
Tsjibbe
01-13-2004, 08:02 AM
Go get yourself Xecuter2.4979_bfm_REPACK.rar from xbins and it will probably solve your problem.
Or do you want use M7 for some reason?
ParisDragon
01-13-2004, 10:14 AM
Well I just read that M7 let people with a non modded virgin xbox not only load and use apps, but also let you eject/insert DVD games for copying to your HDD and they could be played without a lot of change or signing.
My Xbox is v1.0 hardware with 4034 kernel, which I have read is the most compatible for all these mods. So any tips or advice to accomplish my goal is appreciated.
Tsjibbe
01-13-2004, 10:45 AM
Not only this M7 allows you to do this. The xecuter2 bios also works great. Get the latest version in combination with pbl and you can run these apps from every xbox with a production date before half september 2003.
ParisDragon
01-13-2004, 10:59 AM
Ok I also tried the 4980 bios, here is what I did. I extracted the bios files, loaded xbtool since I dont want my evoxdash on my c drive (something tells me MS will figure out to check for other files here eventually). YES I have even tried it on my C drive just to be sure that isnt it. In xbtool I load it as a debug bios with the RC4 from the boot.cfg inserted in the debug.ini. Now I switch it to 1024 in size, click on BFM flag, change my dash location (or not when testing). Now I place it in my 007 savegame under the bioses folder calling it xboxrom.bin. Phoenix loads, sees the file, decrypts it, looks for rbl starting point and executes it, then it either freezes right here with the info still on screen or blanks.
The only thing I think I might have wrong, is someone mentioned I need to fill in my eeprom setting in the phoenix boot.cfg. If I have an xbox 1.0 and kernel 4034 how do I put the proper eeprom setting in there? Phoenix clearly detects my xbox as 1.0 as it should and is trying to use the eeprom 1.0 key to do everything, question is, is that eeprom different for me?
ParisDragon
01-15-2004, 01:54 AM
after much research someone said for it to work on 007 I must start the game, go into a level, quit out and load mission. That changes the sympton alright, it caused the M7 bios to load, little bit of garbage on my xbox screen, however my ExolutionX fails to load, I get an xbox logo screen that sits there, if I push eject cd comes halfway out, goes back in and xbox resets. I just need to get it to let me into the evolutionx now, should I see the white garbo on the screen momentarily?
Do I need to sign evolutionx somehow, btw this evolutionx same copy works fine from the Complex Loader 1.0 I use as my backdoor back in, sine it always seems to work and gives me ftp.
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.