Print

[kotix]

I made some more experience using Liveinfobeta2, here is what I've found out:

1- Changing version will modify the first 30 bytes
2- Changing Video and xbe Region will modify the first 30 bytes
3- Changing the Confounder will modify the first 30 bytes
4- Bytes 30 to 33 will change when I mofify the serial number
5- The serial number is written in the bytes from 34 to 39 with a 3 in front of every number
6- The mac address is written in bytes from 40 to 47
7- The Online key is written in bytes from 48 to 57
8- Dvd kit zone is written in the byte 60, where 00=ff, 01=fe, 02=fd and so on decreasing.

Now, because i guess my confounder number is wrong, I would like to see a valid confounder number from another 1.5 xbox to make a test, so if somebody is reading this tread please post it here, or if somebody can send me an eprom image even if it's a banned one I will really appreciate.

[email protected]

Bye.

[The iNSOMNIAc]

The cofounder is part of the encryption routine that decrypts the real hdd key to unlock the drive. it is part of the sha1 hash algo that uses the drive serial number and xbox serial number( i think). It is xbox specific and pointless trying to get another one from a different xbox..

The problem with the embedded eeprom option is that your box is a v1.5 with a non connexant encoder and as far as i know the linux bios that uses the eeprom patch don`t support it. You get No frag but also No output as no support for the encoder chip.

Try to embed a good eeprom (v1.1 - v1.5) using XBtool 1.0.22 into one of the latest evox bios file and flash your 29 wire homebrew with that. if that works then you did or still do have a messed up eeprom

If any part of the first 48 bytes of the eeprom are NOT correct then the eeprom will fail when loading as the checksums are not correct when they are calculated and checked by the hardware.

[The iNSOMNIAc]

If you have embedded a working eeprom from a v1.1 box into a bios and it still ain`t working then the problem lies elsewhere. with a patched eeprom bios file the board will boot even if there is no real eeprom attached. This leads me to think your problem is with other hardware.

what frag are you getting. Bad eeprom is green for 1 second then just red flashing

[The iNSOMNIAc]

ok then you have tried just about everything eeprom related and it's still the same.

your 29 wire chip is solderd on the bottom side of the board. check all connections on the ram chips for any signs of solder splatter or simmilar. Check for any loose surface mouht resistors or capacitors. Check all 29 points for solder splatter or slight bridges - dry joints.. If you have checked everything above then rebuild the xbox and power up, give it a 30 seconds or so and feel the temp of the mcpx chip. If it burns your finger then you have a major fault on the board. if the mcpx is still pretty cool then it`s time to think a little more.

[The iNSOMNIAc]

Cofounders from a v1. 0000000010A01C00   00000000804A1C00
Cofounder from a v1.1 79D3216AB4655B0E
Cofounder from a v1.3 2B059160B3DE80D0

They do not seem to be specific to each machine if you use liveinfo2 because it still generates a valid eeprom when you save it.. i ain`t tried to load it back to an eeprom yet but it should make no difference.

so problem you have seems again not eeprom related

[kotix]

Ok I agree with you, I uploaded a 1.3 eeprom to my 1.1 xbox and it's working fine, but anyway the backup of the 1.5 on the 1.1 give a black and white screen even if config magic and liveinfo show me a pal eprom; so I guess it has been corrupted somehow.

I'm going to take off the mod recheck everything once again and then put a cheapmod on.

Bye for now.