Post by: afon on March 03, 2004, 11:56:00 AM
But it will be nice to no longer see those ugly scrambles that occur when focus tries to handle the old PBL.
BTW: Did Artifex heel over, or is CE taking all his time away from us?
Post by: shodanjr_gr on March 03, 2004, 12:36:00 PM
BUT
The incompatibility with bios 5530 (which somehow prevents from loading other bioses on RAM) remains. So all of us new XBOX owners are still screwed
Post by: Valhalla1 on March 03, 2004, 01:05:00 PM
I will def. install this one the two focus xbox's I have softmodded, but I'm curious if i should put my 1.0 xbox on this, upgrade from 1.3.5i ?
one of these days I'll get around to flashing the tsop
also -
I'm not finding a signed package.. can I just copy my boot.cfg from 1.3.5i, and sign the default.xbe with -font ?
Post by: Valhalla1 on March 03, 2004, 02:23:00 PM
I used my working boot.cfg from 1.3.5i (they are the same sans the RC4 key)
I tried using both the original jpg's, and the new ones in the rar file
tried using the unsigned xbe, and tried signing it with -font
unsigned of course gives me frag error, the signed one boots to nothing but a black screen and does not get to my dashboard (unleashx, named c:\evoxdash.xbe which works fine with pbl 1.3.5i)
so does this 1.4 not support the original video encoder in my 1.0 (i.e. is pbl 1.4 for focus only?) or did I do something wrong in the signing process
Post by: ddaddy on March 03, 2004, 09:19:00 PM
I wasnt sure what key i was meant to sign with, so tried all 3 of them, habibi, audio, font.
one gave me error 21, and the other 2 went to a black screen.
I have the focus chip and have had 1.3.5i working fine for months.
Post by: Atreyu on March 03, 2004, 09:45:00 PM
i think everyone is going to have to move to Flashing the TSOP
Post by: endo on March 04, 2004, 01:23:00 AM
Post by: Tsjibbe on March 04, 2004, 02:12:00 AM
Post by: Grospolina on March 04, 2004, 06:10:00 AM
| QUOTE (endo) |
| If you don't have a way to recover, I wouldn't screw around with this new "unofficial" version of the PBL. |
If you want to test it, launch it as an application (put it in your Apps folder) and get it to work before replacing your working copy.
BTW everyone, if you don't want to display the logo at all, you can set "Debug true" in your boot.cfg.
Post by: Deagan on March 04, 2004, 08:45:00 AM
But it won't load my bioses :S
Anyone any idea's?
The md5 keys are in my evox.ini but do i need to change the RC4 key to something else?
Bios: 4980.67_BFM.bin / 4980.06_BFM.bin
On any of these i just get a black screen.. nothing more..
Post by: krayzie on March 04, 2004, 10:04:00 AM
Post by: Valhalla1 on March 04, 2004, 11:24:00 AM
of course I dont need 1.4 on this 1.0, but I am testing it and if I can get it to work, I'll put it on my dad's and friend's xbox which have focus chip and they are annoyed by the fuzzy screen. (even with debug true)
Post by: mkjones on March 04, 2004, 02:17:00 PM
| QUOTE (Atreyu @ Mar 4 2004, 07:45 AM) |
| we've got a bigger problem coming.. even if the 5530 kernal issue is solved. there is a newer Kernal just hitting xbox's now 57something or other, which is not allowing a downgraded dash to run at all. i think everyone is going to have to move to Flashing the TSOP |
Bummer, its a shame I guess
More money for the chippers
I hate to say it again but unless there is another Exploit out there that has not been found in these new Dashboards/Kernals then M$ will sadly win
We can live in hope that they didnt do their job properly and a hole appears
Post by: Dunny on March 05, 2004, 04:50:00 AM
Post by: dougyt on March 05, 2004, 09:05:00 AM
Post by: Xboxer190 on March 05, 2004, 12:34:00 PM
Does this alow me to get mordens hack to work on my 5530 I know it will still be scrambled but what do I do to get it to boot mxm/mordens hack
Post by: Grospolina on March 05, 2004, 02:08:00 PM
Maybe 1.4 only works on some Focus chips.
It worked fine on my non-Focus Xbox.
The EvoX backup bios.bin will always be 1MB, even if your chip is 256KB, so that doesn't tell you anything. The sure way to tell what motherboard you have is to open it up. Note that the EEPROM version (1.0-1.1) and the motherboard version (1.0-1.5) are separate numbers (but closely related).
Post by: ZedDedd on March 06, 2004, 08:27:00 PM
tried it still doen's work. BUT here is an interesting link under my new log in (Was grd_42) Crimson Skies Works Pbl!, Heres the simple "quick fix". I tried this "feenix" PBL hack, maybe I heard of it through you, why isn't this more popular? It gets by the clock loop problem with only a minimal effort - have to choose the Phoenix menu item which replaces XBOX LIVE menu item instead of booting directly in. What do you think of it? By the way PBL1.4 default.xbe replace in feenix gives a error 16(?) servicing code.
Thanks,
ZedDedd (grd_42)
Post by: billenglish on March 06, 2004, 08:53:00 PM
Post by: krayzie on March 06, 2004, 09:28:00 PM
Post by: Valhalla1 on March 07, 2004, 12:38:00 PM
| QUOTE (billenglish @ Mar 7 2004, 06:53 AM) |
| you know the 1.4 only works with the standard av pack if it helps anyone... that's why I got rid of it... no 5.1 surround = no fun |
holy shit, THATS what my problem was. =/ i use advanced pack..svideo input, I was getting no audio or video (regular rca audio) well, then maybe I'll go ahead and try it on my dad's 1.4 focus box, he uses standard av and would like to get rid of fuzzy pbl (even with debug true)
Post by: krayzie on March 07, 2004, 02:23:00 PM
Post by: billenglish on March 07, 2004, 03:27:00 PM
Post by: billenglish on March 07, 2004, 03:29:00 PM
Post by: ddaddy on March 07, 2004, 05:37:00 PM
I imagine it works perfect for those using standard av connections.
Anyone tried it on kernel 5530 yet?
Post by: PedrosPad on March 08, 2004, 12:27:00 AM
| QUOTE (Golden Maven @ Mar 4 2004, 08:45 PM) |
| I've read the original thread announcing this release, and someone claimed that he spoke with the Pheonix Loader developpers and they said that Pheonix Loader will most likely never work with the 5530+ kernels. It's something to do with MS removing debug abilities in their new kernels. |
Makes sense. I'm sure Phoenix would have done this if it was simply a minor change.
The shift in emphasis to mod chips begins to make more sense now eh?
Post by: Skallywag on March 08, 2004, 09:08:00 PM
Post by: Bayshido on March 09, 2004, 07:02:00 AM
| QUOTE (ddaddy @ Mar 8 2004, 03:37 AM) |
| OK, i have just tested the new 1.4.1 and it still goes to a black screen. I can however ftp into the xbox which proves the bios and evox have loaded, you just cant see anything. I imagine it works perfect for those using standard av connections. Anyone tried it on kernel 5530 yet? |
test this out please ---------------
When i soft mod i use a evoxd6 bios ,, it even work with the focus chip
Video still scrambled but it wil word ....
but when i got the 5530 i got a black screen
BUT ,,, i can eject and there is no reboot
But i dident cheak if a game wil load
Sorry for the english, but does this make sence
Post by: shodanjr_gr on March 09, 2004, 09:45:00 AM
Post by: soul_reaver_sr on March 09, 2004, 12:28:00 PM
Post by: djresqd on March 09, 2004, 01:03:00 PM
its got kernel 5530
does that mean I cannot softmod it ?
I've tried every pbl version and i keep getting either a black screen or garbled video
I hope I'm just doin something wrong...
If anyone does get pbl up and booting to a alternate dash on a 5530 kernel
Please post "step by step"
Post by: djresqd on March 09, 2004, 03:28:00 PM
used my own kinda custom bios based off x2
It cut a little bit of my screen off so i couldn't read everything
but what i did get to see...
cted bios P:\bioses\xboxrom.bin
ing font
ping Hermes
ing rom P:\bioses\xboxrom.bin
cate 2bl
ing rc4 key:______________________
ypting 2bl
ing 2bl
cting xbox version: 00000000
is version 1.2 1.3 1.4 or 1.5
ing eeprom 1.1 key: __________________
ing eeprom key: ____________________
ing param string
lating 2bl
it locks up right there...
questions ?
do the eeprom keys have to be xbox specific ???
and does the rc4 key have to be anything special?
how do you pull rc4 keys anyway...
Well thats what i found with the focus 5530 box
if anyone know why its doing that or how to fix that ... post
Post by: SpYdErWeB on March 09, 2004, 07:04:00 PM
*PBL 1.4.1 deos NOT fix the bios loading problem with Xbox's with a 5530+ Kernel (really sux).
*Using a standard AV cable PBL 1.4.1 fixes the scrambling screen on both the v1.4 and v1.5.
*Using the Advanced AV Pack or HD Pack causes the screens on both versions of Xbox's to scramble.
Because the screen scrambles with 1.4.1 when using anything but the Standard AV cable, it actually, in my opinion, takes more effort and longer to load than the previous PBL versions.
I recommend that if you are using S-Video or Component cables with your Focus chipped Xbox (as I am with my HDTV), you should stick with PBL 1.3.5i and in the Boot.cfg set your debug to true and timeout setting to 0. This will cut out the loading images and shorten your load time. You will still get a scrambled screen, but it will go away quickly.
If you use 1.4.1, even though the screen is scrambled, you'll have to hit "a" which will take you to the scrambled "Pick your BIOS" screen (which you can't read) and hit "a" again to select xboxrom.bin.
I believe if you leave the first screen on long enough, it may automatically boot your BIOS, but it is still longer than the 1.3.5i I was using...
Come on PBL Team.. give us Home Theater Enthusiasts something to work with!
Post by: Chicken Scratch Boy on March 09, 2004, 07:16:00 PM
Post by: DeltaTau on March 10, 2004, 04:56:00 AM
but as this relqase was not by team pheonix, you shouldnt be blaming them, they have done alot for all the people with softmods
Post by: shodanjr_gr on March 10, 2004, 08:12:00 AM
Video was perfect, no more scrambling.
But still, after i select a bios, i get some text i cant manage to read (goes by real fast) and then a black screen....
And i got no clue as to whats happening...