Print

[opjose]

emailer33:

Why don't you post the specifics of what you did.

We don't need a step by step, merely the general steps.

I'm most curious about the fact that you did not loose your video settings after flashing the blank eeprom, since this is primarily where it screws up.

It's not that I'm doubting you, but your post diverges greatly with what others have reported.

Are you using an NTSC Xbox or a PAL one?
Did you modify the blank EEPROM in any way?

I assume that you unlocked the drive, reflashed then locked it again generating a new PWD (or use the EEPROM utility to do this for you...), is this the case?

What mod chip do you have?

What BIOS?

What rev Xbox and kernel number?

[opjose]

Yeah, which is why I don't understand why he said it works.

I wonder if he merely grabbed the encrypted headers and recalc'd the CRC's.

[emailer33]

QUOTE

What mod chip do you have? What BIOS? What rev Xbox and kernel number?

Modchip: Xodus/Matrix

BIOS: Xecuter 4973 for 1.0 w/ colormod(red) err and nomslogo mods

1.0 XBOX, K Version: 1.00.4973.01

QUOTE

I assume that you unlocked the drive, reflashed then locked it again generating a new PWD (or use the EEPROM utility to do this for you...), is this the case?

nope i left it unlocked after unlocking it w/ the original key.  so w/o a mod, it wouldn't boot anyway.

well i tried to reperform my actions by deleting my dashboard, and then was gonna reapply a backup, just to find out i had deleted it months ago to free space DOH!   .  so i now have the 4627 dashboard rip thanx to complex, but the live update .xbe says that the "disc is damaged" :-P so i gotta go rent a game.  i'll post the tut to what i did after church today and just so you all know, this dashboard problem was my fault, my tut won't make it happen to your's lol.

[undead]

yeah, those eepmod pictures only show the "factory" sections..

it doesnt show the encrypted region (Confounder + HDD Key + XBE Region)

what you could do it dump the configuration to a text file with eeprommer 4.5 and post your configuration here !

[emailer33]

CODE

EEpromer v0.45 by Superfro EEProm Dump Description ======================= Factory Stuff:    HD Key: 00000000000000000000000000000000    HD Password: 278736e04c341b44d4547d715500e1f727b12b990000000053bfde3d84a97a1a    Disk Serial Number: 'WD-WCA9N5207357'    Disk Model Number: 'WDC WD80EB-28CGH2                       '    Game Region: 80000007    Serial Number:    Ethernet Mac Address: 00:00:00:00:00:00    OnlineKey: 00000000000000000000000000000000    Audio / Video Region: 4194560 User Stuff:    Time Zone Offset: 480    Time Zone Standard Name: PST    Time Zone Daylight Name: PDT    Timezone Standard Date:  Month: 10  Day: 5  Day of Week: 0  Hour: 2    Timezone Daylight Date:  Month: 4  Day: 1  Day of Week: 0  Hour: 2    Time Zone Standard Bias: 0    Time Zone Daylight Bias: -60    Language: 1    Video Flags: 0    Audio Flags: 0    Parental Control for Games: 0    Parental Control Password: 0    Parental Control for Movies: 0    Online IP Address: 0    Online DNS Address: 0    Online Default Gateway: 0    Online Subnet: 0    Misc Flags: 0    DVD Region: 0

well that's it

[emailer33]

.  so that's one of the reasons i had to leave the modchip on.  so then i unlocked my HD and applied pixel8's eeprom.  my xbox booted fine and i went to live! jsut to see it say everything in the movie and it connected.  this is pretty much all i did and i hope it helps you.

[shanafan]

I believe error 13 means a bad key, and would make sense because of the HD key being all zeros.

[emailer33]

the description is a dashboard error, as 5-12 is HDD error.

[emailer33]

it's teh same as the one on the xbins ftp.  NO change has been made

[opjose]

Damn what happend to Xbin's login/pwd?

I must have been asleep!?

[BPCaesar]

I thought that when you flashed ur xbox with Pixel8's blank eeprom that it wouldn't display any video at all...what ever happened to this. Or was that just because of the Evox 2.6 bios (including the original) and under not working with modified eeprom images.

[BPCaesar]

btw, pm me, if u need the eeprom

[opjose]

QUOTE (emailer33 @ Dec 22 2002, 08:12 PM)

CODE EEpromer v0.45 by Superfro EEProm Dump Description ======================= Factory Stuff:    HD Key: 00000000000000000000000000000000    HD Password: 278736e04c341b44d4547d715500e1f727b12b990000000053bfde3d84a97a1a    Disk Serial Number: 'WD-WCA9N5207357'    Disk Model Number: 'WDC WD80EB-28CGH2                       '    Game Region: 80000007    Serial Number:    Ethernet Mac Address: 00:00:00:00:00:00    OnlineKey: 00000000000000000000000000000000    Audio / Video Region: 4194560 User Stuff:    Time Zone Offset: 480    Time Zone Standard Name: PST    Time Zone Daylight Name: PDT    Timezone Standard Date:  Month: 10  Day: 5  Day of Week: 0  Hour: 2    Timezone Daylight Date:  Month: 4  Day: 1  Day of Week: 0  Hour: 2    Time Zone Standard Bias: 0    Time Zone Daylight Bias: -60    Language: 1    Video Flags: 0    Audio Flags: 0    Parental Control for Games: 0    Parental Control Password: 0    Parental Control for Movies: 0    Online IP Address: 0    Online DNS Address: 0    Online Default Gateway: 0    Online Subnet: 0    Misc Flags: 0    DVD Region: 0 well that's it

Yeap and I tried all of this too.

It "don't" work.

With the blank numbers using either ConfigMagic or Pixel8's blank EEPROM the XBLive tab bombs out with an error 21 as you've reported.

Restoring the valid headers brings it back to life, albeit with no connection to Xblive.

There is some missing item of information here, which resulted in a valid connection.

I wonder if you were merely utilizing the OLD XBLive dash and getting a valid connection as a result.

The first "update" you would have received via the XBLive service itself should have given you the mod chip detecting version.

The "mod chip" detecting version also bombs out when the headers are all zeros as per Pixel8 or what you posted.

[emailer33]

[opjose]

Except so far it's not reproduceable.

Either you did something different; have a different configuration of some sort; or your not providing some key piece of information (not that I'm saying that you are doing this purposely...).

Other than using the blank Pixel8 eeprom, what did you do?