PBL 1.2 fails to load any retail BIOS

[tutu]

So far I have tried 4817, 5101, Evox D6, Evox D6 Eject fix with Phoenix BIOS loader 1.2 with the audio exploit.

None of them will work.

I am using the same RC4 key that I use with the X2 4977 BIOS which works fine.

I get a blank screen after the Phoenix pic has loaded. Using debug mode the execution stops at "Calling 2bl".

I have EvolutionX on F, and I have modified the Evox D6 BIOSes to look for evoxdash on F. I have also tried an unmodified BIOS and copied EvolutionX to C. Still no go.

I have a v1.1 xbox with 4817 kernel and 4920 dash.

[Iriez]

the BFM 4977 bios uses a DEBUG RC4 , which would not make sense to use with a RETAIL bios.

Though even using the retail 1.0 RC4 with the 3944 and 4034 BFM bios's, i have not had any luck booting them. When enabling debug in the .cfg i get stuck at the "calculating 2bl entry point" message. I have found the same true for every single bios except for the 5558 BFM, and 4977 BFM.

I am farily confident i am using the correct RC4 keys.

[stealth]

Actually it does make sense to use the debug RC4. All bfm bioses are packed with a debug 2bl which is encrypted with the debug key. Even retail bioses which are repacked for bfm. The reason is that it is in the debug 2bl where the support for bfm occurs.

The current problem with the retail bfm bioses (which includes evoxd6 and 2.6), is simply due to a bug in the bios loader. For some reason the eeprom key is not being passed correctly to the retail kernel, and it fails decrypting the eeprom. This is not a problem with debug based kernels (5558, x2) because they don't care if it decrypts or not. Retail ones, however, set the led to fast blinking red and die.

In your case, it is failing at "calculating 2bl entry point" because you are using the wrong RC4 key. Therefore the 2bl is all mangled when it tries to decrypt it.

Hopefully the problem will be fixed in the next version.

This is also the reason certain game saves are not working.

[Iriez]

Thanks for the quick reply stealth. I was not aware that all the BFM kernel's used the debug RC4 ..that will make things much easier.

PS - A simple recommendation would be more documentation surrounding such things as this along with the release....great work = )

Edit-

Using the debug RC4 i got both 3944 and 4034 to boot, but failed to load my dash (error 13) ..which is most likely caused by the fact that i have a 4627 dashboard.

What would be nice is a 4132 and a 4627 BFM release aswell, so we can have all the 1.0-1.2 retail bios's availible = )

...grabbing a 3944 dashboard to check right now if it boots succesfully.

Yup....i put the 3944 dashboard and loaded up the 3944 BFM bios, and it booted straight to the MS dash = ) I assume 4034 would do the same, if i had the dash availible.

Another update:

I installed the 3944 dash, and then played brute force to update the dash to the live dash. I then booted back into evox to relaunch the bios loader into retail mode. It hung on the same 2bl string as it did in my first post. So i shook my head and uploaded the 4034 BFM bios and gave it a whirl ...bam ...works perfect = ) I dont have a xblive account, so i cannot test how it all works out, but hopefully MS will keep their current tolerance and not check our TSOP's or harddrive contents , so long as we cant load up hacked games on their network.

[sektor3]

Tutorials and other tech info will be available from the official homepage for the project soon.

regards,
sektor3

[tutu]

Cool :)

Can't wait for the next release