Post by: vihena on December 29, 2003, 09:59:00 PM
"Manufacturers ID 09 Decide ID 00
!! Flash Not Writeable !!"
I've got a Chameleon currently set to bank 0. I read the manual, but it doesn't seem clear on what "writable" actually is.
I've added all the entries to the ROM and FLASH definitions, and Flashbios,@1 is used. (the ID method doesn't let me select the Flashbios command).
Any help would be appreciated.
Post by: NghtShd on December 30, 2003, 12:25:00 AM
| QUOTE (NeOnRaBbIt @ Dec 29 2003, 05:47 PM) |
| by the way...i think the xbox does modify the fan speed...through xbtool i had it at 70 but wen i checked in that lil program called FanThing it sed it was set at 35...maybe wen it gets to hot the fan increases?? |
FanThing gives the absolute number that the PIC is set to, which has a range of 0-50. XBtool shows the number as a percentage of maximum. So, 70% = an absolute value of 35.
Post by: akillamuthafucca on January 08, 2004, 05:04:00 AM
I tried the hotswap no luck and i'm trying to flash the m7 bios
but is there any way someon can with the
flash not writeable using evox I ass lines to ini file all my other chipas work but this one has me confused
Post by: vihena on January 09, 2004, 07:46:00 PM
Post by: sloerie on January 11, 2004, 05:47:00 AM
| QUOTE (bakin1 @ Dec 16 2003, 09:22 PM) |
| I've been trying yo flash bank 1 on a chameleon for a while. When I try, it just says "erasing" and it stays like that forever, same thing with bank2. I can't try it on bank0 because it has a working bios. Im using mode 1(4x256). any suggestions. |
I am having the same problem, bakin1.
Chameleon on v1.4 box. Flash type: Winbond -WF49F020T
is your flash type the same?
| QUOTE (here are my flash types in evox.ini:) |
Flash = 0x04BA,"ALX2+ R3 FLASH",0x40000 Flash = 0x01a4,"AMD - Am29F040B",0x80000 Flash = 0x01d5,"AMD - Am29F080B",0x100000 Flash = 0x015b,"AMD - Am29LV800B",0x100000 Flash = 0x01da,"AMD - Am29LV800B",0x100000 Flash = 0x378c,"AMIC - A29002",0x40000 Flash = 0x04d5,"FUJITSU - MBM29F080A",0x100000 Flash = 0x04a4,"FUJITSU - MBM29F040C",0x80000 Flash = 0xadb0,"Hynix - HY29F002",0x40000 Flash = 0xadd5,"Hynix - HY29F080",0x100000 Flash = 0x20f1,"ST - M29F080A",0x100000 Flash = 0x20B0,"ST - 29F002",0x40000 Flash = 0xbf61,"SST - 49LF020",0x40000 Flash = 0xbfb6,"SST - 39SF020",0x40000 Flash = 0xda0b,"Winbond - W49F002U",0x40000 Flash = 0xda8c,"Winbond - W29f020",0x40000 Flash = 0x0900,"Winbond - W49F020T",0x40000 #Unconfirmed: Flash = 0xc236,"MACRONIX - MX29F022NTPC",0x40000 Flash = 0x89a6,"SHARP - LH28F008SCT",0x100000 |
Post by: brian1234 on January 12, 2004, 12:11:00 PM
!! Unknown Flash Type !!"
i get this error trying to flash my x2.3lite+ with the x2 4980.06 bios.
anyone know how to fix this?
Post by: RedBizkit on January 14, 2004, 10:57:00 AM
Any ideas!
Also with 4980
Post by: ripster on January 26, 2004, 03:42:00 PM
[Misc]
# Retail HD config Created by SlaYer for the SlaYer's EvoX Auto-Installer v2.5
AutoLaunchGames = No
AutoLaunchDVD = No
DVDPlayer = "e:Appsdvdxdefault.xbe"
AutoLaunchAudio = Yes
#AudioPlayer = "c:xboxdash.xbe"
MSDashBoard = "c:xboxdash.xbe"
UseFDrive = Yes
UseGDrive = Yes
SkinName = Gears
IGR = Yes
UseItems = No
ScreenSaver = 10
Fahrenheit = Yes
ShadeLevel = 90
EnableSMART = Yes
HDD_Temp_ID = 194
DebugTSR = No
ChameleonLed = 15
GameRegion = 0
[Network]
SetupNetwork = Yes
StaticIP = Yes
Ip = 192.168.1.200
Subnetmask = 255.255.255.0
Defaultgateway = 192.168.1.1
DNS1 = 194.63.248.1
DNS2 = 217.13.7.140
SkipIfNoLink = Yes
SetupDelay = 5
[IGR]
Start_Button = Yes
Back_Button = Yes
L_Trig = Yes
R_Trig = Yes
White_Button = No
Black_Button = No
A_Button = No
B_Button = No
X_Button = No
Y_Button = No
[Clock]
JumpToMsDash = No
JumpIfNoLink = Yes
Use24 = NO
SNTP_Server = 216.244.192.3
SwapDate = Yes
[FTP]
Enable = Yes
#Username = xbox (this cannot be changed)
Password = xbox
IGR = Yes
[RDTOOLS]
Enable = Yes
Name = SlaYers_EvoX
IGR = Yes
[BIOS]
#
ROM = "Original 3944",0x542C62CB976A4993C8C5027DFF9638CE
ROM = "Original 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "EvoX 2.0",0x76fd88337b8d8c1f116f85f3984b98b6
ROM = "EvoX 2.1",0x99487615bb30670cb65993388fcf2a63
ROM = "EvoX 2.2",0x220ade778785cfc3c98bb5ea8bbd8608
ROM = "EvoX 2.3",0x057C9D0480FD498C91081DF50DD1F6DD
ROM = "EvoX 2.4",0xE3CE66B99957A92FDAC40AF951C3F1FD
ROM = "EvoX 2.5",0x5ad8e13005fa3e3383227c4bdb0ad85f
ROM = "EvoX 2.3 no logos",0x855EF706E264351B056124CB538BDF56
ROM = "EvoX 2.3 no ani",0x92BB4AFBBCBF4CF7DC376418286A8930
ROM = "EvoX 2.3 fast ani",0x9C0654469CC90C33A7D54AC79C374380
ROM = "EvoX 2.4 err no logo",0xE0109F21892D475D1DA1CBECC244C601
ROM = "EvoX 2.4 err no ani",0xE03C7AF969933C821B4375E0D3DB6022
ROM = "EvoX 2.4 err ybox nl",0x3E66E6832BC2C5D19C0637AEF00C7EDD
ROM = "EvoX 2.4 err ybox na",0xD4CC70976EAE2D849627ADDC02997819
ROM = "EvoX 2.5 err na nl",0x1ABC74B2B154160FFEE366A8479BF7B7
ROM = "EvoX 2.5 err na nl evox",0xDDF255F5D4F4F3912A419FE278116C2D
ROM = "EvoX 2.5 err na nl ybox",0x3F752E5381C9CC53D5DF8C28F4D68F71
ROM = "EvoX 2.5 col err",0x688497922D63AF6385C8E37E1C19EADA
ROM = "EvoX 2.5 col err evox",0x097C581438C69DE515A346D19A9D9C41
ROM = "EvoX 2.5 col err S6T9",0x064af70778c01214d3924825838fa6a2
ROM = "EvoX 2.5 col err ybox",0xFFDCCDDF7DDCF0ADB0C2FC70752BC7A1
ROM = "EvoX 2.5 col err no ani",0xE1BF3D54A5F347C01645D4CA713568A6
ROM = "EvoX 2.5 cm err na evox",0x48626499F85FBAF53A6DFE360F8CDE2E
ROM = "EvoX 2.5 cm err na ybox",0x8BC27C5CBE5810B9C6A53C9D95B1DE14
ROM = "EvoX 2.6",0xdd3de3542bff7b36cdb0dbe078c27fbe
ROM = "EvoX 2.6 Ej Fix",0x2e1ec59dc8c295b462d5bffa73feaecc
ROM = "EvoX 3.6",cb73b4914bb6c70b66e21377989726a0
ROM = "EvoX 3.6ef",0xf754767b388ce7a08bf57304e24c9ae9
#
ROM = "EvoD.6",0xc349c2b047a3d6c2de2e1c10185ecf86
ROM = "EvoD.6ejct",0x74c6235497f474bf88b54b3fc52a20b2
ROM = "EvoD.6 red",0xef744b3cb11a616ca79177170f4841cd
ROM = "EvoD.6 red",0xa2d334ef382382eb1233aa95e9bb1bcd
ROM = "EvoD.6 blue",0x04788b6a2c0ae55a2670d162a71151dc
ROM = "EvoD.6 blue E",0xf21291e0f6c234bbbd1ad0e69bfc463d
ROM = "EvoD.6 blue F",0x6d963467af0a93fc636fae7f50e713c3
ROM = "EvoD.6ej blue",0x67ea6aa22a3b0e64b68912e41ef7d109
ROM = "EvoD.6ej blue E",0x5272c09256bdfb1cf94a75c11ea45c1d
ROM = "EvoD.6ej blue F",0x1764e6c46898a55c7c601d14bfb7dae8
ROM = "EX D.6 blue F",0x6e1686b410a1a80a2025e73aa3f50394
ROM = "EvoD.6ej na blue ",0xb2d87f04ef0486851998f35e87f0fb78
ROM = "EvoD.6ej na blue E",0x1470758c30266c47c031da09aec4b46e
ROM = "EvoD.6ej na red",0x39b989b3ba404b3a67d9d2ae11dc1c57
ROM = "EvoD.6ej na red E",0xb63c6ef67db45cab00aad2b603541264
ROM = "EvoD.6ej red F",0xb283ba81df4ca67055331d6fd2893ca9
ROM = "EvoD.6ej na blue",0xcd3158097fd98aa65ba271024fb6c23a
ROM = "EvoD.6ej na blue E",0xfc1ae335b061e3a88d04d3bf18d8e55e
ROM = "EvoD.6ej na red",0xa2d334ef382382eb1233aa95e9bb1bcd
ROM = "EvoD.6ej na red E",0xa2d334ef382382eb1233aa95e9bb1bcd
ROM = "EvoXD6_MP",0x738e892e7cb1bf90d836eb205b61a667
ROM = "tsop_d6",0x4ac893ee574617462ad399051d093492
#
ROM = "EvoX M7",0x93db270779f5b964f50be075a5d5d2d2
ROM = "EvoX M7ej",0xf0980189407abca8d1f8d823621beaf0
ROM = "EvoX M7ej",0xe7b7fe715c4f4a8293618979f7dfbab1
ROM = "EvX M7ej FC",0x3aa68fa95dc833cb4614c6e6f767e117
ROM = "EvoX M7 ej noani",= 0x79cb96f56c4e6d153bb57a1a7c62ebd0
ROM = "Evx M7ej+137G",0x896583ad185e35ee4ad14776c02ed30f
ROM = "Evx M7ej+137G RED",0x703538B6200BEE92186BC1209C675D14
#
ROM = "CPX 4034",0xcf36ad116e2404aff022533b07b11004
ROM = "CPX v1.0 Debug",0xfd1ac8ba0033df93e2da2a23009272e4
ROM = "CPX v1.0",0x4132e24c64b7a8d4ea34ff448051e923
ROM = "CPX v1.02 Debug",0x8E5C811CCC3C6875FD90C4D0ED6A8ABF
ROM = "CPX v1.02 Debug no ani",0xAC65F68F2706235A578FE1C5FB1E41B1
ROM = "CPX v1.02",0x70B54E6CD91F59D4932E7ED776F9267E
ROM = "CPX v1.02 kina",0x84efef3ee91ac320dab4778881108938
ROM = "CPX v1.02 no logo",0xA993FCC9D41FAE1C7AB7759077CC77BF
ROM = "CPX v1.02 no ani",0x3621FE90ED6438DFA9E57897B0631E2D
ROM = "CPX v1.03 Debug",0xB701B33BD1281E9541970AD9112161C6
ROM = "CPX v1.03",0x21445C6F28FCA7285B0F167EA770D1E5
ROM = "Trapflags v1",0x80EE2CFBF7AF617BB42256B572AC6640
ROM = "Trapflags v2",0xAEE3AEA34AC62C823A165DB632A22709
ROM = "Pandora",0xF8D2682275B2EA41EE213FFAAF2FC96A
ROM = "Pandora",0xC87A3FA22D7985B98689B1D9645C2822
ROM = "Xtender v1.0",0xE89B1A394E21D07E54864C229E9763F0
ROM = "Xtender v1.1",0x2D5E2953911D278AA38A273C0F6E0E41
ROM = "Xtender v1.3",0x96015F442D345A6FDC9915CAFCBC63A4
ROM = "Xecuter v1",0x5D540DFBA44B8C7EE3826CBADFA04491
ROM = "E-X Final 4034",0xE78262E21CE24644415D96D9DF6F64E4
ROM = "E-X Beta 4034",0xF9BA842542D980CB3186FA6EC55F9909
ROM = "E-X Beta2 4034",0x563830D746868117D5AD57AA67203CA2
ROM = "TATX Dual Debug",0xC998CA2882D14B430E8AAC0BC08B045A
ROM = "TATX Dual Debug VGA LameOne",0xe5049c482d96461cad1a245c374653ed
ROM = "Bluecop 4627 Debug",0x844ff9e0fc7f7bd01ec5e75b10aece62
ROM = "Linux v0.1 BL",0xa2146859548ea11d16f5c235aceb45e8
ROM = "Xbox Rec CD Debug",0x3dde2f4a0b772f6619f30c151339b8b7
ROM = "Xbox Rec CD Retail",0x0716573694b60111fe24b834c3531c9d
ROM = "Linux v0.1 BL",0xa2146859548ea11d16f5c235aceb45e8
ROM = "Cromwell 1.8 256k",0xd5bc60eaf462ee1d697ae2853d93d933
ROM = "OzXBios (Cromwell) v1.26a 256k",0x6d62d25b98a8238748181b609cfb4ace
ROM = "OzXBios (Cromwell) v1.26a 1MB",0xe46ceeb049b1805f8042a58521f02f81
ROM = "Xbox Rec CD Debug",0x3dde2f4a0b772f6619f30c151339b8b7
ROM = "Xbox Rec CD Retail",0x0716573694b60111fe24b834c3531c9d
ROM = "Dominion-X 0901 F 256k",0x975d1d8bfc080bea86717f933406c9bb
ROM = "Dominion-X 0901 F 512k",0x975d1d8bfc080bea86717f933406c9bb
ROM = "Dominion-X 0901 F 1Mb",0x975d1d8bfc080bea86717f933406c9bb
ROM = "Dominion-X 0901 G 256k",0x2a6a12ca344fbe6c78effb7981c2a667
ROM = "Dominion-X 0901 G 512k",0x2a6a12ca344fbe6c78effb7981c2a667
ROM = "Dominion-X 0901 G 1Mb",0x2a6a12ca344fbe6c78effb7981c2a667
#
ROM = "Xecuter2 1.0",0x8ed3428fd664a999914c40702bf4126c
ROM = "Xctr2 v1 E na blu",0xb9c981c01653db282437fea40f3757aa
ROM = "Xctr2 v1 F na blu",0x1b27c7a7c5ea50043a54cb1c22a14a98
ROM = "Xctr2 v1 na blu",0x23f0867c60846e20272ce9e33bdd7121
ROM = "Xctr2 v1 na",0x98fd3f4ba71e593a47f0409abc77abea
ROM = "Xctr2 v1 E na",0x40cf68929ec1807b56f66fbe8f97dc40
ROM = "Xctr2 v1 F na",0x8144977d633402d6fbff3b5516d6b3d0
ROM = "Xctr2 v1 E",0xa8c225b0f80ee87e80c2b3d8f588b158
ROM = "Xctr2 v1 F",0xff43ba5ba464fb3b6c3fddb880a029d0
ROM = "X2 LITE",0x94928743972d443385721e5b92e5f7fb
ROM = "X2 xbox1.0 _1mb",0x18ae3a651037c6ac8a7bb19497193c57
ROM = "X2 xbox1.0 256k",0x94928743972d443385721e5b92e5f7fb
ROM = "X2 xbox1.1 1mb",0xf6e885e88590c9aa625e3ca5f0744390
ROM = "X2 xbox1.1 256k",0xa154577a223e2de097195dae062a4f10
ROM = "X2 xbox1.1 4x256k",0xc92a29a5db0d7d43abe1ee750b35184b
ROM = "X2 xbox1.1 512k",0x4fc144f5395dc3e59ef984a681c740ee
ROM = "Xctr2 4972 1.1",0xd040bb919beb57222f2e7bdd3137ba94
#
ROM = "X2 v1 4973 XMAS err noani 1MB",0x6f361492a12711a5dfa817907aad72a4
ROM = "X2 v1 4973 XMAS err noani 256k",0x7c461eb216db48672e0675daf564ae6e
ROM = "X2 v1 4973 XMAS err noani 512k",0xf51151c8206d9545f57bb2de8e895d18
ROM = "X2_4973 xbox1.0 256k",0x7137c693e67554b92873d3ec5cdbb1d8
ROM = "X2 4973 xbox1.1 _256k",0xb4f9a0c9f363c49751268ed0bd4126e4
ROM = "X2 4973 v1 B",0x35beadd82f45b66c376084a5e62445f5
ROM = "X2 4973 *F*",0x5d4acfa53bbc8895b770826fc8a0af82
ROM = "X2_4973 1.0 err greyblack",0xf8ea175f240103b40a9012b75c2090b2
ROM = "X2 4973 1.0 err greyblack noani",0x9b451a9d461032502af5f6c80273f15a
ROM = "X2 4973 1.0 err noani purple",0xfbdc76f603fb02bb72f0c7d7f6fbda04
ROM = "X2 4973 1.0 err orange",0x1643553d1b7e3e0df44168ca3d921eb9
ROM = "X2 4973 1.0 err orange2",0x21f7fde45eef3a3ded4cea1df356f324
ROM = "X2 4973 1.0 err_orange2 noani",0x172bcb1cf9d2321a0b11ef90667f40ab
ROM = "X2 4973 1.0_err orange noani",0x7b8911066591b9bfcb83d020dfc010bb
ROM = "X2 4973 1.0 err purple",0x1233c919bd2727c2ff4e6bb6f962fb78
ROM = "X2 4973 1.0 err redblue",0x30f54976e4d0bf9f4209d2abf6bc7fa5
ROM = "X2 4973 1.0 err redblue noani",0x658916109e8ab9ed3d3cf5f241c58b21
ROM = "X2 4973 1.0 err white",0xb9a041e73582be89412ce9c3be0dc1b3
ROM = "X2 4973 1.0 err white noani",0xb479f510fbd88167d7e47ced230b41a9
ROM = "X2 4973 err purpleorange",0x6b76f248de4656ed32f401f6141f8a9c
ROM = "X2 4973 err purpleorange f",0x1264a52daa0e86466371370fd0790983
ROM = "X2 4973 err purpleorange noani",0x56347f13fdacc2bfd233cfeb57885b72
ROM = "X2 4973 err whitered",0xedc808af34f8594fbcfad20dc2dd79e9
ROM = "X2 4973 err whitered noani",0xeacb9df2b9c1222e06dfe6d5c94655f0
ROM = "X2 4973 xbox1.0 err blue 256k",0x2108e89c8af9dc599e968e36278731af
ROM = "X2_4973 xbox1.0 err noani 256k",0xf2f8c4e3fc29c847b0050a829832da0b
ROM = "X2 4973 xbox1.0 err noani blue 256k",0x6f4e270ab1056a85d58377b9510a3eab
ROM = "X2 4973 xbox1.0 err noani red 256k",0x2321ea1b81934015855ebe89e0b7600c
ROM = "X2 4973 xbox1.0 err_red 256k",0x20433436b4718d75c4999489d34d4802
#
ROM = "X2 4974",0x24bff933c4ee6178040ab4b4daf6c6a8
ROM = "X2 4974 Blue",0xaa5fe4306525b8e951fbe0069022572e
ROM = "X2 4974 blue",0xdefc13e707ae004def6faef030bf6fed
ROM = "X2 4974 blue e",0x3f350289c2ef5fce2576b4b3af215a7c
ROM = "X2 4974 blue f",0xbc30074e1676a9a21afd75f761bd7301
ROM = "X2 4974 blue nologo",0x1a0c398cd2df743ee0431c620a228fe0
ROM = "X2 4974 blue nologo e",0x33e34aef14bacbb7da9b6af54dd5d299
ROM = "X2 4974 blue nologo f",0x38cdf647e913ab48c18c083e4772d4a5
ROM = "X2 4974 MultiVer 256k",0x24bff933c4ee6178040ab4b4daf6c6a8
ROM = "X2 4974 MultiVer noani blue nologo e",0x6a302e9de90d210662879f3a2b7535d5
ROM = "X2 4974 MultiVer noani f",0x5b812ddc682fdd464b8a60fca775d872
ROM = "X2 4974 noani",0x31afdc9df4577272f7006be1634fffc5
ROM = "X2 4974 noani blue",0xaa5fe4306525b8e951fbe0069022572e
ROM = "X2 4974 noani blue e",0xa3f571a3e0c6c5a60a2812c42a30f64d
ROM = "X2 4974 noani blue f",0xcbd70e3bcbf64305ccb8b2ee7ef362a7
ROM = "X2 4974 noani blue nologo",0xd87090c540b74bad1e1de6fc552b3ec2
ROM = "X2 4974 noani e",0x7211257fe524c66b1f748d10aeb920d8
ROM = "X2 4974 noani f",0x5b812ddc682fdd464b8a60fca775d872
ROM = "X2 4974 No Logo",0x02010F772F9316A1E5F60F03D337FA74
ROM = "X2 4974 red",0x475fde28d0aaeada9ebf932ce2c4beb9
ROM = "X2 4974 red",0x0c6084c2fdec4f76e3f9aeedcec978e3
ROM = "X2 4974 red e",0xe9f956274eaf50027984dbaeeeed4481
ROM = "X2 4974 red f",0x81f8db8d8c33cf15c1951b4c54aa1c23
ROM = "X2 4974 red nologo",0x2c968b5d7cb8301aaa8a3fff0bb3c716
ROM = "X2 4974 red nologo e",0x264ce8a8e2fb47e9e7e007c8bf773e07
ROM = "X2 4974 red nologo f",0x6797f132dd392553e7e5c7e191994a3d
#
ROM = "X2 4976 *F*",0x18ef84ee6332da4d54c211c3c04146e1
Rom = "X2 4976.02 256",0x1e259481510639d69c8223f75bd79b9b
Rom = "X2 4976.02 512",0x0d7829378e5fd7d112c617d76cac31d7
Rom = "X2 4976.02 1MB",0x1e259481510639d69c8223f75bd79b9b
ROM = "X2 4976.02 DkBlue NoAni 256k",0x2d667670ef9493b0211a13ed3ce7fc02
ROM = "X2 4976.02 Orange noani 256k",0xd7cbaece6dae5df28a05326ad83d16b2
ROM = "X2 4976.02 Purple noani 256k",0xe8a202a7b3392a3a187cdee08f63e1e9
ROM = "X2 4976.02 Red noani 256k",0x52bd0523971bbe5671beedf9c9d314ab
ROM = "X2 4976.02 Silver noani 256k",0x5faf05479a8b0d45e6744af120e4b45c
ROM = "X2 4976.02 Yellow noani 256k",0x54cc7f3c042bea41278de529210411ba
ROM = "X2 4976.02.noani.nologo",0x547e27a3c0ec33b301725e7b76552b94
ROM = "X2 4976.02.blue.F.256k",0x08846888cdb3329f16e7483727f826cf
ROM = "X2 4976.02.blue-red.F.256k",0x46055fa98962c8089d6d292769fa2078
ROM = "X2 4976.02 *F*",0x379340c28e4742cc9d6edc783ffeee4c
#
ROM = "X2 4977",0x92987e26edd5833921c9b0e539ea091e
ROM = "X2 4977 *F* B",0x5a0998981aa739c2778dfbeb7f985b2f
ROM = "X2 4977 *F* B",0x352679aefa71bdd4fe160fb7dd7d8343
ROM = "X2 4977 *F* P",0xbbf8e9a67ebf5d75899a8b030f6ffb24
ROM = "X2 4977 Dark Blue",0xd612e7ee1f58a76298d67f39246a8d1c
ROM = "X2 4977 Blue",0xc4c2dcb8714c3a0d6cdb40213172f6e7
ROM = "X2 4977 Gray",0x860746a3d229c8851e1f98d45fad546b
ROM = "X2 4977 Green",0xe853ca313e1e2d57418cf1759ae73f6b
ROM = "X2 4977 Orange no ani",0x9dbf36b33590b073e1b5f71f36438b12
ROM = "X2 4977 Purple",0x5888771b9c6308ea5433151cd277a033
ROM = "X2 4977 Red",0x00e4ac5dee193d2bcd14910c89732103
ROM = "X2 4977 red/red noani",0xaacae34cf419053714b305cf8bdbd129
ROM = "X2 4977 green noani",0xe853ca313e1e2d57418cf1759ae73f6b
ROM = "X2 4977 LBA48 noani G",0xc3e4354d2d33aed2cf2625e32f1f86f1
ROM = "X2 4977 LBA48 noani F",0x045fb02c7cb3235a020c260a79e3e3d7
ROM = "X2 4977 orange/orange noani",0x8becb160e8c0a493ec25868d7e7a6ce1
ROM = "X2 4977 F",0x21e7047cc0ce3802dc22ea291883b56f
ROM = "4977 FC BlueR",0x4bd2b7b7a03535a34177e1efd06eb176
ROM = "X2 4977 FC",0xc64ac26c8c583b6b44024747565e0103
ROM = "4977 FC+137G",0x117dcad2de59c7e1ec85216fa9106166
ROM = "4977 FC137BR",0x5d06a5caa5e434b6024ec6fab55700cb
#
ROM = "X2 4978",0x6e77d14a22f7235a2da3f67e809d1c6b
ROM = "X2 4978 IP0.9",0xd577c8c35720169b0f758c42dddbe18a
ROM = "X2 4978.BUG.FIX",0xfccf1a68440e486e04c3ad605febef12
ROM = "X2 4978.FIXLAUNCH10",0x3341291f5030071e3cc8e8eb2ccccb4e
ROM = "X2 4978.02",0x23ed933c4ea395d1a7f30701f68a857d
ROM = "X2 4978.03",0xe432af482dd624427fc3cf6ce2589489
#
ROM = "ALX2-RED",0x5355AA0F40396F68B2D9ED30BFF3BDA2
ROM = "ALX2-BLUE",0xFC16FA0620367B713CD47F8532B7F6BD
#
Flash = 0x04d5,"FUJITSU - MBM29F080A",0x100000
Flash = 0x04a4,"FUJITSU - MBM29F040C",0x80000
Flash = 0xadd5,"Hynix - HY29F080",0x100000
Flash = 0xadb0,"Hynix - HY29F002",0x40000
Flash = 0x20f1,"ST - M29F080A",0x100000
Flash = 0x20B0,"ST - 29F020",0x40000
Flash = 0xbfb6,"SST - 39SF020",0x40000
Flash = 0xbfb7,"SST - 39SF040",0x80000
Flash = 0x04BA,"ALX2+ R3 FLASH",0x40000
Flash = 0x378c,"AMIC - A29002",0x40000
Flash = 0x01d5,"AMD - Am29F080B",0x100000
Flash = 0x015b,"AMD - Am29LV800B",0x100000
Flash = 0x01a4,"AMD - Am29F040B",0x80000
Flash = 0x01da,"AMD - Am29LV800B",0x100000
Flash = 0xda0b,"Winbond - W49F002U",0x40000
Flash = 0xda8c,"Winbond - W29f020",0x40000
Flash = 0xc236,"MACRONIX - MX29F022NTPC",0x40000
Flash = 0x89a6,"SHARP - LH28F008SCT",0x100000,0x20,0xd0,0x10
# for Matrix/Xodus
Flash = 0xbf61,"SST - 49LF020",0x40000
# for Xecuter2
Flash = 0x01d5,"XECUTER2",0x100000
Current = 0x896583ad185e35ee4ad14776c02ed30f
[Skin_Original]
#
# <Time> =
# <IP> =
# <Name>
# <Version>
# <CD>
# <BIOSVer>
# <KernelVer>
# <RDName>
# <Temp1>
# <Temp2>
# <SpaceC>
# <SpaceE>
# <SpaceF>
# <SpaceG>
# <SpaceX>
# <SpaceY>
# <SpaceZ>
#
Text = 30,37,0.5,0x000000,0,"<Time><CrLf>MB Temp <Temp1><CrLf>CPU <Temp2>"
Text = 28,39,0.5,0x808080,0,"<Time><CrLf>MB Temp <Temp1><CrLf>CPU <Temp2>"
Text = 620,420,0.5,0x000000,1,"<Name> V<Version>"
Text = 618,422,0.5,0x808080,1,"<Name> V<Version>"
Text = 620,37,0.5,0x000000,1,"<CD>"
Text = 618,39,0.5,0x808080,1,"<CD>"
Text = 30,420,0.5,0x000000,0,"RD Name : <RDName>"
Text = 28,422,0.5,0x808080,0,"RD Name : <RDName>"
LogoType= 0
[Menu]
Section "Root"
{
Item "Play Game or Media from DVDROM Drive",ID_Launch_DVD
Section "Play Games from HD"
{
Line "- Games on the Hard Drive -",2
AutoAddItem "E:GAMES"
AutoAddItem "E:HDDLoader"
SortAll
}
Item "Game Trainers",ID_trainer
Item "DVD MOVIE Player - Region Free","e:AppsDVDXdefault.xbe"
Section "Self Installed Emulators"
{
Line "- Emulators on Hard Drive -",2
SortStart
AutoAddItem "e:AppsEmulators"
SortEnd
}
Item "Xbox Media Player - XBMP","e:AppsXBMPdefault.xbe"
Item "XboX Gentoo LINUX - Self Add-On","e:gentooxx.xbe"
Section "System Management"
{
Item "Game Management on Xbox HD","e:AppsHDDLoaderdefault.xbe"
Item "Game and Media Backup Tool","e:AppsDvD2XboXdefault.xbe"
Item "Choose a Different Skin",ID_Skins
Section "Launch Apps from HD"
{
Line "- Media and File Managers -",2
Item "Dvd2Xbox Media Copier","e:AppsDvd2Xboxdefault.xbe"
Item "PxHDD Loader","e:AppsHDDLoaderdefault.xbe"
Item "Xbox File Explorer","e:AppsboXplorerdefault.xbe"
Line "- Auto Added Items -",2
SortStart
AutoAddItem "e:Apps"
SortEnd
}
Item "MS Dashboard - Use to change Time/Date and TV Settings",ID_MS_Dash
Item "System Settings",ID_Settings
Item "Flash BIOS",ID_Flash_Bios.
Section "System"
{
Item "Settings",ID_Settings
Item "Flash BIOS",ID_Flash_Bios
Item "Backup",ID_Backup
Item "Skins",ID_Skins
}
Item "Reboot Xbox",ID_Quick_Reboot
Item "Power OFF Xbox",ID_Power_Off
}
[Action_10]
[Action_11]
[Action_12]
[Telnet]
Enable = Yes
Post by: [UFK]Hitman on February 02, 2004, 09:38:00 AM
I have aladin advanced modchip....my computer guru says that this modchio can crash if he flashes it and then i have to do it my self
but jeh...i dont understand the .ini file part...can someone give me the part with the Flash part :$ please :$ i want to flash the modchip with the EvoX M7(Eject FiX) I am scared about his words, becaus he told me that then if the flashing goes bad then i would have to change the modchip
this is bad...but how can i be sure that my flash will be OKAI...??? realy newb here! Been searching and reading for all day but still nothing...please help
Post by: dark_shadow on February 04, 2004, 02:21:00 AM
I had the same problem with my Aladdin Advance modchip. Didn't know the exact ini settings but I tried to flash it. And yes, it went wrong. I ended up with a dead modchip.
After searching the internet I found an other flash tool, it's called "Xflash SST49lf020 v2" it's specially for the Aladdin modchips. I've tried it with many boises and they all work ! But make sure you use a bios size of 256kb.
Maybe you should try that one, it worked for me.
Greetzz
Post by: [UFK]Hitman on February 04, 2004, 05:49:00 AM
I have the 256k evox M7 bios and they say that it will work
i hope so...But like i understand then i just ftp the files to xbox harddrive and flash it
easy==?? no need to change evox.ini file??Edit: But i have a xFlash , but i dont know what version.. the name is like xFlash_b002.zip???
Okai i found the xFlash you told
i will try then 
Post by: juanelo_123 on February 05, 2004, 06:33:00 AM
my problem is that the bios of my xbox I erase I need a help please
what I can do?
Post by: iamxbox on February 08, 2004, 02:52:00 AM
Can I use any?
Post by: dark_shadow on February 10, 2004, 05:38:00 AM
Use 4981.67 if you're planning to use a HD > 137 GB
You can use any bios you like but it has to be compatible with your Xbox version and the size must be 256K !
You can compare different bioses on THIS page.
Greetz
Post by: billou2k on February 14, 2004, 04:47:00 PM
I've got the matrix, evox 3921 running an old bios I havent updated since I've installed the cip a long time ago.
I wanted to update the bios to the 4981.06. The erasing process in evox was quite long and then the "flashing BIOS now!" just lasts forever... And of course the xbox doesnt restart anymore
Any reason?
Well hopefully I'll manage to find where I put the programmer and after a few hours I'll manage to rewrite a bios on it... fingers crossed...
Post by: billou2k on February 15, 2004, 08:57:00 AM
I could find the matrix programmer and luckily this time it went faster than last time, The programmer could upload the bios on the chip on the first try.
And I could restart the xbox with the latest executer 2 bios with no problem!
Post by: cjs118 on February 28, 2004, 03:58:00 PM
I am wondering where i put the bios that i want to reflash the chip with, because when i look in my system menu on the evox.ini file there is no area that has the option for "FlashBios."
On the actual EvoX disc there is a folder that contains 4 diff. bioses. Wouldn't i be able to save the new bios in that folder so Evox would load that bios from the folder?
Please Help!
Post by: cjs118 on February 28, 2004, 10:31:00 PM
I did not get it to work the way i wanted it to. I originaly had a 4977 1MB bios on the chip. I wanted to reflash it the 4977 512K on one bank and the 4981.67 512K on the other bank. So i made a 1MB bios consisting of the two bioses. When i used the EvoX reflashing program it was successful except for when i try to use the bios on bank 2, it just frags.
Please Help!
Post by: tonloc79 on June 14, 2004, 09:07:00 PM
Post by: thorFlea on June 24, 2004, 08:18:00 AM
Post by: BlissfullyIgnorant on June 26, 2004, 11:45:00 PM
I want to start by apologising for my abrubt appearance on this forum and the irrelevance of my question. I bought my Xbox on Monday and since then have bought and personally intalled a SmartXX modchip. I flashed it with Executer2 BIOS (X2 4977). The first time i did this, i flashed it into a bank that i had previoulsy erased out of ignorance of what i was doing. Although it appeared to work, when i rebooted, both my SmartXX boot screen and the original bios were both in black and white and Executer2 didnt seem to have been flashed as the start up screen still said 'MS'
. Confused, i re-flashed the second bank with X2. This seemed to work better, and the next time i booted the start up screen read Executer2. It was however still in black and white. I later realised that the Video settings for the SmartXX screen were set to NTSC. When i changed this back to PAL the SmartXX screen returned to colour but the Original Bios still remains black and white. I have gone on to install the Evolution X Dashboard, but it still remains black and white. If anyone has any ideas pls help me as i am becoming more and more disheartened about the future of my xbox 
. Thank youBlissfullyIgnorant
Post by: Ditomopyge on June 28, 2004, 08:26:00 AM
I have seen that you can run 2 different BIOS's, each in 2 256k banks, but can you use 4 different BIOS's each in a 256k bank on the X2.3b Pro (since I have noticed that you can select indiviual banks with the DIP switch provided)?
Post by: pooh2pooh on July 26, 2004, 10:54:00 AM
I am a little confused. I have searched through many forums with no clear answers to my questions.
I have a xecuter 2.3b lite+ installed. I have decided to use the x2 4981.06 bios. I understand that the next step is to flash the bios. Do I do this by creating a disc with just the bios on it, or do I need to create and iso with the bios included in the iso, or some other option that I haven't caught on to.
Also how large do I need to make my bios? The Chip has two banks. Each bank is 512 if I understand correctly. So do my bios need to be 512 or 1024.
Thanks
Post by: OuTbReAk on October 20, 2004, 01:58:00 AM
Post by: cykage on December 05, 2004, 01:39:00 AM
Post by: Scratchy on July 30, 2005, 08:41:00 AM
newbie question: I have an X-b.i.t modchip, and it came with a usb cord that hooks up to my computer, from a board attached on the outside of my xbox, is that considered a programmer?
Post by: voxic on October 22, 2006, 03:18:00 PM
Post by: btheman on January 12, 2007, 08:32:00 AM
Please help.
Post by: theperfekt001 on January 12, 2007, 09:26:00 AM
Post by: btheman on January 12, 2007, 10:05:00 AM
Post by: Unreal7000 on May 31, 2003, 10:25:00 PM
Requirements:
-Xbox with an installed mod-chip - X2, Matrix, etc
-XBTool - http://home.alltel.net/nghtshd/xbtool.html
-Evo-X Dashboard - installed of course
-BIOS that you want - I recommend X2 4981.06 or X2 4981.67 to find which is right for you go here: http://xbox-scene.com/xbox1data/news-archi...e-9-11-2003.php
If you plan on doing color mods then you need to stear clear of the 4983 series as theses are encrypted and there is currently no way of doing the color mods.
-Punching Bag (Optional) - Don't worry this is only if something goes wrong.
WARNING: If you do this wrong you could ruin your mod-chip. Neither I nor Xbox-scene.com or any affiliates are responsible for the damages that could take place.
READ THIS: If you just bought your mod-chip and it is an X2.2 anything (pro, lite, or liteplus) or X2.3 anything then you need to follow this tutorial first.
http://forums.xbox-scene.com/index.php?act...ST&f=16&t=89545
If your wondering where to get software for your Xbox (EvoX, X2 Bios, Emulators, etc) check here: http://www.Xbox-scene.com/articles/xbins.php
TERMS:
B.I.O.S. - firmware used to start the Xbox up and tell the Xbox just exactly what it is capable of doing.
Virgin BIOS - BIOS that has had no modifications done to it.
Flash - process of writing the new firmware to the chip.
Now that we got that out of the way we can get to the fun stuff!
Once you have downloaded your BIOS (.BIN format) you will want to open it up in XBTool.
First thing that you will want to do is verify the BIOS MD5. This is located at the top of the program. To do this look go to
http://forums.xbox-scene.com/index.php?act...ST&f=38&t=43437
see if the BIOS you are using has the hash markings as the one on that site(I think they're HEX).
So lets say you have a virgin 1MB X2 4976.02 BIOS, make sure the hash marks are identical (usually if the first 5 or 6 numbers match then your golden, but just make sure they all match).
From here you are free to change the colors or remove animation etc in XBtools.
These are completely optional and I recommend NOT doing these options the first time, unless you just really want to.
Once you have made the wanted changes make sure you match the "file size" with the maximum that your mod-chip supports. Example: The X2 comes with a 1MB BIOS. But the Matrix comes with 256K.
You can see what size your BIOS supports here: http://www.Xbox-scene.com/modchips3b.php
Once you have double checked everything hit "Save As" and name it something so that you will remember. Example: "Xecuter 4976.02 Orange NoAni 1MB" (Orange Boot up and No animation) or "Xecuter 4976.02 Virgin 1MB". NOTE: If you are making NO changes (Means BIOS is the correct SIZE and you are not changing any of the colors) then you dont need to save it.
Now you will want to FTP into your Xbox and go to the C drive, if there is not a folder called "Bios" then make one. Once thats done put the BIOS that you will use into that folder. If your booting evox off a cd, make sure you have your bios in the bios folder on that cd.
Check your evox.ini file to make sure you have somthing in the "Menu" that looks like the following:
Item "Flash BIOS",ID_Flash_Bios.
Section "System"
{
Item "Settings",ID_Settings
Item "Flash BIOS",ID_Flash_Bios
Item "Backup",ID_Backup
Item "Skins",ID_Skins
}
Item "Reboot",ID_Quick_Reboot
Item "Power Off",ID_Power_Off
If the the "Flash BIOS" turns red and won't let you access it, then change it to Item "Flash BIOS",@1
The next part is optional but i highly recommend it.
If you look around in the evox.ini file you will notice some lines that look SIMILAR to this:
[BIOS]
#
ROM = "Bluecop 4627 Debug",0x844ff9e0fc7f7bd01ec5e75b10aece62
ROM = "CPX 1.02 Debug no ani",0xAC65F68F2706235A578FE1C5FB1E41B1
ROM = "CPX 4034",0xcf36ad116e2404aff022533b07b11004
ROM = "CPX v1.0 Debug",0xfd1ac8ba0033df93e2da2a23009272e4
ROM = "CPX v1.0",0x4132e24c64b7a8d4ea34ff448051e923
ROM = "CPX v1.02 Debug no ani",0xAC65F68F2706235A578FE1C5FB1E41B1
ROM = "CPX v1.02 Debug",0x8E5C811CCC3C6875FD90C4D0ED6A8ABF
ROM = "CPX v1.02 kina",0x84efef3ee91ac320dab4778881108938
#
This is a database of how EvoX recognizes what BIOS is currently flashed on your modchip.
I recommend going back to
http://forums.xbox-scene.com/index.php?act...ST&f=38&t=43437
and copying all of it and replacing it with what was in [BIOS] or you can add it to what was already there. However, lets say you customized your BIOS (using XBTools) and it doesn't match any of them that are in the list. You can make your own. Heres how:
ROM = "BIOS Name",hash
"BIOS Name" is where you fill in what you want Evo-X to say.
Example: "Xecuter 2 4976.02 blue noani 1MB"
Hash is the hash of the BIOS. To get this fire up XBTool and open your customized BIOS and copy down the BIOS MD5 hash (No need to save since you aren't making changes).
Make sure you put the 0x in first.
Now Evo-X will recognize what BIOS you have and will display it in the settings.
On a side note some people have told me that you may also need something like this in your evox.ini file (check and see if something similar is there, if its not there put it there):
Flash = 0x01d5,"AMD - Am29F080B",0x100000
Flash = 0x04d5,"FUJITSU - MBM29F080A",0x100000
Flash = 0xadd5,"Hynix - HY29F080",0x100000
Flash = 0x20f1,"ST - M29F080A",0x100000
Flash = 0xbf61,"SST - 49LF020",0x40000
Now comes the worst part of all. I do not recommend doing this during a storm, rolling blackouts, or whenever there is a chance of the power going out. If for some reason you turn-off or lock up the Xbox while it is flashing or erasing the BIOS then you will need the dreaded Punching Bag.
-Turn off Xbox.
-Open up your Xbox: http://www.xbox-scene.com/articles/open1.php
-Disable the flash protection. (For Matrix owners put it in mode 4, both dip switches OFF.)
-Put Xbox back together and turn on.
-Go to "Flash BIOS" under "Settings" and hit X. You should see your customized BIOS.
-Hit X and then it will say something on the screen that says "Press Y to flash". Press Y and ONLY press Y if you have double checked and researched everything.
-Once you hit Y it will go through the process of erasing and installing your new BIOS. The whole process takes about 20-30 seconds.
-Afterwards it will say "Your Xbox will power off" Wait till it powers off and with fingers crossed turn on your Xbox and you should see that it is working. If not pull out Punching Bag and hit repeatedly until you feel somewhat better.
-If for some reason a bad flash did occur and you own a X 2.X lite/lite plus your not all that much out of luck, for around 15$ you can buy a programmer that hooks up to your PC and allows you to flash it from there. http://shop.system-mods.com/product.asp?3=95
-For instructions on how to flash your modchip with a programmer check here: http://forums.xbox-scene.com/index.php?act...ST&f=50&t=63396
-If for some reason you get an error when you try to flash or it locks up in the middle of the flash process, there is a 99% chance you forgot to remove the flash protection. I can't tell you how many time people have instant messaged me with this question.
-If it is booting up then go to the settings of Evo-X and scroll down to see if it recognizes what BIOS you have installed. If it says "Unknown" then you can either ignore it or you can read what I wrote above. I like to have it display my BIOS that way if I forget.
-Now you can open back up your Xbox and put the flash protection back on (dont want little kids accidently flashing your BIOS now do you). You can either keep the Bios that you put in your Bios folder in the C drive of your Xbox for future use or you can delete it. It is no longer required for your Xbox to work.
I recommend reading this thoroughly, and doing some research for your mod-chip. Did someone say Google? Please do not instant message me asking for the BIOS because im sick of responding to those messages. Only serious questions pertaining to mod-chip flashing will be answered.
Thanks to Dink for telling me about the Flash part in the evox.ini file.
Thanks to Katana-Sama for filling me in on information about the Matrix mod-chip.
Happy Flashing
Unreal7000
This post has been edited by Unreal7000: May 11 2004, 12:55 PM
Post by: Neanderthal on June 01, 2003, 02:01:00 PM
However, I have a slight problem in that with my homebrew (cheapmod) chip, in the "backup" folder on C: the bios.bin is 1,024kb in size so obviously I create a 1024k bin of the 4976.2 bios. I've then uploaded this new bin to my newly created c:bios directory.
Then after a reboot of the xbox, I can see the new bios in the "flash bios" but when I select it I'm told file size error?
Now being foolish I created a 256k version of the bios and tried flashing that but it got stuck on "erasing...." I reached for a punchbag but to my surprise, when I rebooted the Xbox it worked ok and is still on the old bios (4974.01)
What am I doing wrong?
Post by: Unreal7000 on June 01, 2003, 03:24:00 PM
Post by: CeREaL on June 01, 2003, 06:30:00 PM
i thought at first i phucked my box cuz it would lock up at the splash screen but i took off the bios switch jumper on my x2lite and same thing but i pressed the eject button to reset the box while it froze and my blue bios loaded so that worked and i made a different bios with diff features and fixed up the locking up in 5 minutes thanks soo much now all my games load
Post by: Unreal7000 on June 02, 2003, 11:12:00 PM
Post by: blindguy on June 05, 2003, 09:33:00 AM
If you have a CheapMod.com mod chip, you must remove the jumper in order to flash the bios. Normally the CheapMod's ship with the jumper on to disable flashing the chip.
Also, the backup feature in EvoX writes a 1024k bios.bin file even though the CheapMod bios chip is only 256k. The bios.bin file in the backup directory is really four copies of the 256k bios. So you need a 256k bios file to flash your CheapMod.
Chris
Post by: Unreal7000 on July 10, 2003, 03:59:00 PM
Post by: trevlenOO6 on July 10, 2003, 08:22:00 PM
Post by: Unreal7000 on July 11, 2003, 06:21:00 AM
If you want to have 2 Bios then do the following:
If you are starting out with a virgin 1MB Bios .bin file then,
use a bios slicer so you can get it down to 4 256k pieces. http://dwl.xbox-scene.net/~xbox/xbox-scene...XBiosSlicer.zip
From there use X2 Bios Manager http://dwl.xbox-scene.net/~xbox/xbox-scene...s/bios/x2bm.zip
Select Image Size 1024k.
Then select the first bank 256k.
Hit Import and then select one of the 256k .bin files you just created.
Now hit copy and then select second bank 512 and hit paste.
The first and second bank should be the same BIOS now.
Now for the last two banks do the same thing except choose a different BIOS that you want.
Then hit save. Now you have a 1MB BIOS that has two different BIOS on it.
After you flash you can remove jumper (1.0/1.1) on the chip to choose which BIOS you want.
Post by: bombzhome on July 11, 2003, 10:52:00 AM
Post by: dink on July 11, 2003, 02:53:00 PM
I have spent many hours searching for something like this. Instead, I put together my evox.ini from various threads.
As I recall, I had to add in the evox.ini, the type of flash chip, in order to flash it. I did not see it in your turtorial.
Flash = 0x01d5,"AMD - Am29F080B",0x100000
Flash = 0x04d5,"FUJITSU - MBM29F080A",0x100000
Flash = 0xadd5,"Hynix - HY29F080",0x100000
Flash = 0x20f1,"ST - M29F080A",0x100000
Flash = 0xbf61,"SST - 49LF020",0x40000
Post by: trevlenOO6 on July 11, 2003, 04:47:00 PM
Post by: SaSh on July 15, 2003, 10:51:00 AM
| QUOTE (Unreal7000 @ Jun 1 2003, 07:18 AM) |
| Item "Flash BIOS",ID_Flash_Bios |
First of all , I have to say this is a "good to understand guide " . I'm not done with it ... i have to go to a shop to get those different screwdrivers
But I've made all the preparations. And i have this question :I have this line :
Item "Flash BIOS",@1
in my evox.ini ........
Does that make any difference ?
Post by: Unreal7000 on July 15, 2003, 01:06:00 PM
Post by: nix2k on July 15, 2003, 02:23:00 PM
As far as I know, anyone using X2 chips just need that line in their flash section. As for other chips, no idea, I use an X2.1 lite, and thats the line you need.
Post by: jdub2169 on July 22, 2003, 12:41:00 AM
Post by: the haunted on July 26, 2003, 09:31:00 AM
Post by: Unreal7000 on July 27, 2003, 07:37:00 PM
Post by: Hydro69 on July 29, 2003, 05:34:00 PM
I would like to know what and were to change.
I guess I should put my ini here- well just the menu part:
[Menu]
Section "Root"
{
Item "Play Game from DVDROM Drive / RESET",@5
Section "Play Games from HD"
{
Line "- Games on the Hard Drive -",2
SortStart
AutoAddItem "f:HDDLoader"
SortEnd
}
Item "DVD MOVIE Player","f:AppsDVDXdefault.xbe"
Item "Xbox Media Player","f:AppsXBplayerdefault.xbe"
Item "Power OFF Xbox",@10
Section "System Management"
{
Item "Game Management on Xbox HD","f:AppsHDDLoaderdefault.xbe"
Item "Choose a Different Skin",@13
Section "Launch Apps from HD"
{
Item "Xbox File Explorer","f:AppsboXplorerdefault.xbe"
Line "- Self Copied Items -",2
SortStart
AutoAddItem "f:Apps"
SortEnd
{
Item "MS Dashboard - Use to change Time/Date and TV Settings",@3
Item "Flash Bios",ID_Flash_Bios
Item "System Settings",@9
}
Thanks.
Post by: Unreal7000 on July 29, 2003, 07:34:00 PM
Item "Flash Bios",ID_Flash_Bios
to
Item "Flash BIOS",@1
Post by: Ginie66 on August 01, 2003, 07:37:00 AM
but i am editing my evoX.ini (in the 007 rain coat) so i can flash the bios using 007 rain coat using the mem card one for 1mb and 512mb (flashing the tosp 1/2 and 1/2 or wholely)and the second one is now for flashing 256k bios now i am make my second one and having a bit of truble with the 265k ones i will post my ini if any spots any probs pls let me now sorry if it is long i am not sure if there are length limits
another question does the it mater or do i have to config each ROM to Each bios
[Misc]
# Master config file for SlaYer's EvoX Auto-Installer v2.1
#
# Edit [Network] section to tweak IP settings for your Network if necessary!
AutoLaunchGames = No
AutoLaunchDVD = No
DVDPlayer = "f:Appsdvdxdefault.xbe"
AutoLaunchAudio = Yes
#AudioPlayer = "c:xboxdash.xbe"
MSDashBoard = "c:xboxdash.xbe"
UseFDrive = Yes
SkinName = SlaYer21
[Network]
SetupNetwork = Yes
StaticIP = Yes
Ip = 192.168.0.22
Subnetmask = 255.255.255.0
Defaultgateway = 192.168.X.X
DNS1 = 0.0.0.0
DNS2 = 0.0.0.0
[Clock]
JumpToMsDash = No
JumpIfNoLink = Yes
SNTP_Server = 216.244.192.3
Use24 = Yes
SwapDate = Yes
[FTP]
Enable = Yes
#Username = xbox (cannot be changed)
Password = xbox
[RDTOOLS]
Enable = Yes
Name = EvoX
[BIOS]
#
ROM = "Original 3944",0x542C62CB976A4993C8C5027DFF9638CE
ROM = "Original 4034",0xF20CD7574BB4B2A69810B2E9F766A90D
ROM = "EvoX 2.0",0x76fd88337b8d8c1f116f85f3984b98b6
ROM = "EvoX 2.1",0x99487615bb30670cb65993388fcf2a63
ROM = "EvoX 2.2",0x220ade778785cfc3c98bb5ea8bbd8608
ROM = "EvoX 2.3",0x057C9D0480FD498C91081DF50DD1F6DD
ROM = "EvoX 2.4",0xE3CE66B99957A92FDAC40AF951C3F1FD
ROM = "EvoX 2.5",0x5ad8e13005fa3e3383227c4bdb0ad85f
ROM = "EvoX 2.3 no logos",0x855EF706E264351B056124CB538BDF56
ROM = "EvoX 2.3 no ani",0x92BB4AFBBCBF4CF7DC376418286A8930
ROM = "EvoX 2.3 fast ani",0x9C0654469CC90C33A7D54AC79C374380
ROM = "EvoX 2.4 err no logo",0xE0109F21892D475D1DA1CBECC244C601
ROM = "EvoX 2.4 err no ani",0xE03C7AF969933C821B4375E0D3DB6022
ROM = "EvoX 2.4 err ybox nl",0x3E66E6832BC2C5D19C0637AEF00C7EDD
ROM = "EvoX 2.4 err ybox na",0xD4CC70976EAE2D849627ADDC02997819
ROM = "EvoX 2.5 err na nl",0x1ABC74B2B154160FFEE366A8479BF7B7
ROM = "EvoX 2.5 err na nl evox",0xDDF255F5D4F4F3912A419FE278116C2D
ROM = "EvoX 2.5 err na nl ybox",0x3F752E5381C9CC53D5DF8C28F4D68F71
ROM = "EvoX 2.5 col err",0x688497922D63AF6385C8E37E1C19EADA
ROM = "EvoX 2.5 col err evox",0x097C581438C69DE515A346D19A9D9C41
ROM = "EvoX 2.5 col err S6T9",0x064af70778c01214d3924825838fa6a2
ROM = "EvoX 2.5 col err ybox",0xFFDCCDDF7DDCF0ADB0C2FC70752BC7A1
ROM = "EvoX 2.5 col err no ani",0xE1BF3D54A5F347C01645D4CA713568A6
ROM = "EvoX 2.5 cm err na evox",0x48626499F85FBAF53A6DFE360F8CDE2E
ROM = "EvoX 2.5 cm err na ybox",0x8BC27C5CBE5810B9C6A53C9D95B1DE14
ROM = "EvoX 2.6",0xdd3de3542bff7b36cdb0dbe078c27fbe
ROM = "EvoX 2.6 Ej Fix",0x2e1ec59dc8c295b462d5bffa73feaecc
ROM = "EvoX 3.6",cb73b4914bb6c70b66e21377989726a0
ROM = "EvoX 3.6ef",0xf754767b388ce7a08bf57304e24c9ae9
#
ROM = "EvoD.6",0xc349c2b047a3d6c2de2e1c10185ecf86
ROM = "EvoD.6ejct",0x74c6235497f474bf88b54b3fc52a20b2
ROM = "EvoD.6 red",0xef744b3cb11a616ca79177170f4841cd
ROM = "EvoD.6 red",0xa2d334ef382382eb1233aa95e9bb1bcd
ROM = "EvoD.6 blue",0x04788b6a2c0ae55a2670d162a71151dc
ROM = "EvoD.6 blue E",0xf21291e0f6c234bbbd1ad0e69bfc463d
ROM = "EvoD.6 blue F",0x6d963467af0a93fc636fae7f50e713c3
ROM = "EvoD.6ej blue",0x67ea6aa22a3b0e64b68912e41ef7d109
ROM = "EvoD.6ej blue E",0x5272c09256bdfb1cf94a75c11ea45c1d
ROM = "EvoD.6ej blue F",0x1764e6c46898a55c7c601d14bfb7dae8
ROM = "EvoD.6ej na blue ",0xb2d87f04ef0486851998f35e87f0fb78
ROM = "EvoD.6ej na blue E",0x1470758c30266c47c031da09aec4b46e
ROM = "EvoD.6ej na red",0x39b989b3ba404b3a67d9d2ae11dc1c57
ROM = "EvoD.6ej na red E",0xb63c6ef67db45cab00aad2b603541264
ROM = "EvoD.6ej red F",0xb283ba81df4ca67055331d6fd2893ca9
ROM = "EvoD.6ej na blue",0xcd3158097fd98aa65ba271024fb6c23a
ROM = "EvoD.6ej na blue E",0xfc1ae335b061e3a88d04d3bf18d8e55e
ROM = "EvoD.6ej na red",0xa2d334ef382382eb1233aa95e9bb1bcd
ROM = "EvoD.6ej na red E",0xa2d334ef382382eb1233aa95e9bb1bcd
#
ROM = "Xecuter2 1.0",0x8ed3428fd664a999914c40702bf4126c
ROM = "Xctr2 v1 E na blu",0xb9c981c01653db282437fea40f3757aa
ROM = "Xctr2 v1 F na blu",0x1b27c7a7c5ea50043a54cb1c22a14a98
ROM = "Xctr2 v1 na blu",0x23f0867c60846e20272ce9e33bdd7121
ROM = "Xctr2 v1 na",0x98fd3f4ba71e593a47f0409abc77abea
ROM = "Xctr2 v1 E na",0x40cf68929ec1807b56f66fbe8f97dc40
ROM = "Xctr2 v1 F na",0x8144977d633402d6fbff3b5516d6b3d0
ROM = "Xctr2 v1 E",0xa8c225b0f80ee87e80c2b3d8f588b158
ROM = "Xctr2 v1 F",0xff43ba5ba464fb3b6c3fddb880a029d0
ROM = "Xctr2 4973 v1",0x7137c693e67554b92873d3ec5cdbb1d8
ROM = "Xctr2 4972 1.1",0xd040bb919beb57222f2e7bdd3137ba94
ROM = "Xctr2 4974",0x24bff933c4ee6178040ab4b4daf6c6a8
ROM = "X2 LITE",0x94928743972d443385721e5b92e5f7fb
ROM = "X2 4974 red",0x0c6084c2fdec4f76e3f9aeedcec978e3
ROM = "X2 4974 No Logo",0x02010F772F9316A1E5F60F03D337FA74
ROM = "X2 4974 Blue",0xDEFC13E707AE004DEF6FAEF030BF6FED
ROM = "X2 4974 Blue",0xaa5fe4306525b8e951fbe0069022572e
ROM = "X2 4974 Red",0x475FDE28D0AAEADA9EBF932CE2C4BEB9
ROM = "X2 4974 Blue No Logo",0x1A0C398CD2DF743EE0431C620A228FE0
ROM = "X2 4974 Red No Logo",0x2C968B5D7CB8301AAA8A3FFF0BB3C716
ROM = "X2 4973 v1 B",0x35beadd82f45b66c376084a5e62445f5
ROM = "X2 4973 *F*",0x5d4acfa53bbc8895b770826fc8a0af82
#
ROM = "X2 4976 *F*",0x18ef84ee6332da4d54c211c3c04146e1
ROM = "X2 4976.02",0x1e259481510639d69c8223f75bd79b9b
Rom = "X2 4976.02",0xd7cbaece6dae5df28a05326ad83d16b2
Rom = "X2 4976.02",0x52bd0523971bbe5671beedf9c9d314ab
Rom = "X2 4976.02 Orange Noani",0xd7cbaece6dae5df28a05326ad83d16b2
Rom = "X2 4976.02 Red Noani",0x52bd0523971bbe5671beedf9c9d314ab
Rom = "X2 4976.02 Purple Noani",0xe8a202a7b3392a3a187cdee08f63e1e9
Rom = "X2 4976.02 Silver Noani",0x5faf05479a8b0d45e6744af120e4b45c
Rom = "X2 4976.02 Yellow Noani",0x54cc7f3c042bea41278de529210411ba
Rom = "X2 4976.02 DkBlue Noani",0x2d667670ef9493b0211a13ed3ce7fc02
ROM = "X2 4976.02 *F*",0x379340c28e4742cc9d6edc783ffeee4c
#
ROM = "CPX v1.0 Debug",0xfd1ac8ba0033df93e2da2a23009272e4
ROM = "CPX v1.0",0x4132e24c64b7a8d4ea34ff448051e923
ROM = "CPX v1.02 Debug",0x8E5C811CCC3C6875FD90C4D0ED6A8ABF
ROM = "CPX v1.02 Debug no ani",0xAC65F68F2706235A578FE1C5FB1E41B1
ROM = "CPX v1.02",0x70B54E6CD91F59D4932E7ED776F9267E
ROM = "CPX v1.02 kina",0x84efef3ee91ac320dab4778881108938
ROM = "CPX v1.02 no logo",0xA993FCC9D41FAE1C7AB7759077CC77BF
ROM = "CPX v1.02 no ani",0x3621FE90ED6438DFA9E57897B0631E2D
ROM = "CPX 4034",0xcf36ad116e2404aff022533b07b11004
ROM = "CPX 4627 v1.02 Debug",0x70D6F0B58D5A7EB84611B76225AD4E08
ROM = "CPX 4627 v1.02",0x70B54E6CD91F59D4932E7ED776F9267E
ROM = "CPX 4627 v1.03 Debug",0xB71494C46A6B3010C97AC040E4889DCE
ROM = "CPX 4627 v1.03",0x3D2C1A663C523F08389180A868B3D335
ROM = "Trapflags v1",0x80EE2CFBF7AF617BB42256B572AC6640
ROM = "Trapflags v2",0xAEE3AEA34AC62C823A165DB632A22709
ROM = "Pandora",0xC87A3FA22D7985B98689B1D9645C2822
ROM = "Xtender v1.0",0xE89B1A394E21D07E54864C229E9763F0
ROM = "Xtender v1.1",0x2D5E2953911D278AA38A273C0F6E0E41
ROM = "Xtender v1.3",0x96015F442D345A6FDC9915CAFCBC63A4
ROM = "Xecuter v1",0x5D540DFBA44B8C7EE3826CBADFA04491
ROM = "E-X Final 4034",0xE78262E21CE24644415D96D9DF6F64E4
ROM = "E-X Beta 4034",0xF9BA842542D980CB3186FA6EC55F9909
ROM = "E-X Beta2 4034",0x563830D746868117D5AD57AA67203CA2
ROM = "Bluecop 4627 Debug",0x844ff9e0fc7f7bd01ec5e75b10aece62
ROM = "Linux v0.1 BL",0xa2146859548ea11d16f5c235aceb45e8
ROM = "Xbox Rec CD Debug",0x3dde2f4a0b772f6619f30c151339b8b7
ROM = "Xbox Rec CD Retail",0x0716573694b60111fe24b834c3531c9d
#
ROM = "X2 LITE",0x94928743972d443385721e5b92e5f7fb
ROM = "X2_4973 1.0 err greyblack",0xf8ea175f240103b40a9012b75c2090b2
ROM = "X2 4973 1.0 err greyblack noani",0x9b451a9d461032502af5f6c80273f15a
ROM = "X2 4973 1.0 err noani purple",0xfbdc76f603fb02bb72f0c7d7f6fbda04
ROM = "X2 4973 1.0 err orange",0x1643553d1b7e3e0df44168ca3d921eb9
ROM = "X2 4973 1.0 err orange2",0x21f7fde45eef3a3ded4cea1df356f324
ROM = "X2 4973 1.0 err_orange2 noani",0x172bcb1cf9d2321a0b11ef90667f40ab
ROM = "X2 4973 1.0_err orange noani",0x7b8911066591b9bfcb83d020dfc010bb
ROM = "X2 4973 1.0 err purple",0x1233c919bd2727c2ff4e6bb6f962fb78
ROM = "X2 4973 1.0 err redblue",0x30f54976e4d0bf9f4209d2abf6bc7fa5
ROM = "X2 4973 1.0 err redblue noani",0x658916109e8ab9ed3d3cf5f241c58b21
ROM = "X2 4973 1.0 err white",0xb9a041e73582be89412ce9c3be0dc1b3
ROM = "X2 4973 1.0 err white noani",0xb479f510fbd88167d7e47ced230b41a9
ROM = "X2 4973 err purpleorange",0x6b76f248de4656ed32f401f6141f8a9c
ROM = "X2 4973 err purpleorange f",0x1264a52daa0e86466371370fd0790983
ROM = "X2 4973 err purpleorange noani",0x56347f13fdacc2bfd233cfeb57885b72
ROM = "X2 4973 err whitered",0xedc808af34f8594fbcfad20dc2dd79e9
ROM = "X2 4973 err whitered noani",0xeacb9df2b9c1222e06dfe6d5c94655f0
ROM = "X2 4973 xbox1.0 err blue 256k",0x2108e89c8af9dc599e968e36278731af
ROM = "X2_4973 xbox1.0 err noani 256k",0xf2f8c4e3fc29c847b0050a829832da0b
ROM = "X2 4973 xbox1.0 err noani blue 256k",0x6f4e270ab1056a85d58377b9510a3eab
ROM = "X2 4973 xbox1.0 err noani red 256k",0x2321ea1b81934015855ebe89e0b7600c
ROM = "X2 4973 xbox1.0 err_red 256k",0x20433436b4718d75c4999489d34d4802
ROM = "X2 4974",0x24bff933c4ee6178040ab4b4daf6c6a8
ROM = "X2 4974 blue",0xdefc13e707ae004def6faef030bf6fed
ROM = "X2 4974 blue e",0x3f350289c2ef5fce2576b4b3af215a7c
ROM = "X2 4974 blue f",0xbc30074e1676a9a21afd75f761bd7301
ROM = "X2 4974 blue nologo",0x1a0c398cd2df743ee0431c620a228fe0
ROM = "X2 4974 blue nologo e",0x33e34aef14bacbb7da9b6af54dd5d299
ROM = "X2 4974 blue nologo f",0x38cdf647e913ab48c18c083e4772d4a5
ROM = "X2 4974 MultiVer 256k",0x24bff933c4ee6178040ab4b4daf6c6a8
ROM = "X2 4974 MultiVer noani blue nologo e",0x6a302e9de90d210662879f3a2b7535d5
ROM = "X2 4974 MultiVer noani f",0x5b812ddc682fdd464b8a60fca775d872
ROM = "X2 4974 noani",0x31afdc9df4577272f7006be1634fffc5
ROM = "X2 4974 noani blue",0xaa5fe4306525b8e951fbe0069022572e
ROM = "X2 4974 noani blue e",0xa3f571a3e0c6c5a60a2812c42a30f64d
ROM = "X2 4974 noani blue f",0xcbd70e3bcbf64305ccb8b2ee7ef362a7
ROM = "X2 4974 noani blue nologo",0xd87090c540b74bad1e1de6fc552b3ec2
ROM = "X2 4974 noani e",0x7211257fe524c66b1f748d10aeb920d8
ROM = "X2 4974 noani f",0x5b812ddc682fdd464b8a60fca775d872
ROM = "X2 4974 red",0x475fde28d0aaeada9ebf932ce2c4beb9
ROM = "X2 4974 red e",0xe9f956274eaf50027984dbaeeeed4481
ROM = "X2 4974 red f",0x81f8db8d8c33cf15c1951b4c54aa1c23
ROM = "X2 4974 red nologo",0x2c968b5d7cb8301aaa8a3fff0bb3c716
ROM = "X2 4974 red nologo e",0x264ce8a8e2fb47e9e7e007c8bf773e07
ROM = "X2 4974 red nologo f",0x6797f132dd392553e7e5c7e191994a3d
ROM = "X2 v1 4973 XMAS err noani 1MB",0x6f361492a12711a5dfa817907aad72a4
ROM = "X2 v1 4973 XMAS err noani 256k",0x7c461eb216db48672e0675daf564ae6e
ROM = "X2 v1 4973 XMAS err noani 512k",0xf51151c8206d9545f57bb2de8e895d18
ROM = "X2_4973 xbox1.0 256k",0x7137c693e67554b92873d3ec5cdbb1d8
ROM = "X2 4973 xbox1.1 _256k",0xb4f9a0c9f363c49751268ed0bd4126e4
ROM = "X2 xbox1.0 _1mb",0x18ae3a651037c6ac8a7bb19497193c57
ROM = "X2 xbox1.0 256k",0x94928743972d443385721e5b92e5f7fb
ROM = "X2 xbox1.1 1mb",0xf6e885e88590c9aa625e3ca5f0744390
ROM = "X2 xbox1.1 256k",0xa154577a223e2de097195dae062a4f10
ROM = "X2 xbox1.1 4x256k",0xc92a29a5db0d7d43abe1ee750b35184b
ROM = "X2 xbox1.1 512k",0x4fc144f5395dc3e59ef984a681c740ee
#
ROM = "MS 3944 512K",0x46eba6c23bfa9ed3184cd12aa95b0c02
ROM = "MS 3944 1MB",0xe8b39b98cf775496c1c76e4f7756e6ed
ROM = "MS 4034 512K",0x687ff9c95707c034e77b3909cfa1dc04
ROM = "MS 4034 1MB",0xb49a417511b2dbb485aa255a32a319d1
ROM = "MS 4817.01 256K",0xc3db66c8e212974afec6d6087ddbb8ef
ROM = "MS 4817.01 512K"0x37985ba9ca2963e4d3b31df8b06d11b3
ROM = "MS 4817.01 1MB"0x430b3edf0f1ea5c77f47845ed3cbd22b
ROM = "X2 4977 NROEF 256K",0x92987e26edd5833921c9b0e539ea091e
ROM = "X2 4977 NROEF 512K",0x06fa78f0abb1632f3676fa566f964395
ROM = "X2 4977 NROEF 1MB",0xf51878ca4506080394428173b62ab1ea
#
Flash = 0x01d5,"AMD - Am29F080B",0x100000
Flash = 0x04d5,"FUJITSU - MBM29F080A",0x100000
Flash = 0xadd5,"Hynix - HY29F080",0x100000
Flash = 0x20f1,"ST - M29F080A",0x100000
Flash = 0xbf61,"SST - 49LF020",0x40000
Flash = 0xbfb6,"SST - 39SF020",0x40000
Flash = 0x01a4,"AMD - Am29F040B",0x80000
Flash = 0xda0b,"Winbond - W49F002U",0x40000
Flash = 0xc236,"MACRONIX - MX29F022NTPC",0x40000
# for Matrix/Xodus
Flash = 0xbf61,"SST - 49LF020",0x40000
# for Xecuter2
Flash = 0x01d5,"XECUTER2",0x100000
Current = 0x1e259481510639d69c8223f75bd79b9b
[Skin_Original]
#
# <Time> =
# <IP> =
# <Name>
# <Version>
# <CD>
# <BIOSVer>
# <KernelVer>
# <RDName>
# <SpaceC>
# <SpaceE>
# <SpaceF>
# <SpaceX>
# <SpaceY>
# <SpaceZ>
#
Text = 30,37,0.5,0x000000,0,"<Time>"
Text = 28,39,0.5,0x808080,0,"<Time>"
Text = 620,420,0.5,0x000000,1,"<Name> V<Version>"
Text = 618,422,0.5,0x808080,1,"<Name> V<Version>"
Text = 620,37,0.5,0x000000,1,"<CD>"
Text = 618,39,0.5,0x808080,1,"<CD>"
Text = 30,420,0.5,0x000000,0,"RD Name : <RDName>"
Text = 28,422,0.5,0x808080,0,"RD Name : <RDName>"
LogoType= 0
[Menu]
Section "Root"
{
Item "1) RESET / REBOOT",@5
Line "------------------------------------",2
Item "2) Save BIOS / EEPROM (XBOX C:backup)",@11
Line "------------------------------------",2
Section "3) FLASH Full TSOP 1MB v1.0 or v1.1"
{
Line "--- W A R N I N G! ---",1
Line "-- THIS CAN KILL YOUR XBOX! --",1
Section "I understand the risks and & I want to continue"
{
Line "-- COULD KILL YOUR XBOX ! --",1
Item "3-1) Flash TSOP 1MB with EvoX-D.6 EjectFix",@270
Line "------------------------------------",2
Item "3-2) Flash TSOP 1MB with Xecuter2-4976.02",@271
Line "------------------------------------",2
Item "3-3) Flash TSOP 1MB with Xecuter2-4977 NROEF",@272
Line "- Needs Both Bridge Points on MB!-",1
}
Line "- Read TSOP Tutorials First! -",1
}
Line "------------------------------------",2
Section "4) FLASH 1/2 TSOP 512K v1.0 or v1.1"
{
Line "--- W A R N I N G! ---",1
Line "-- THIS CAN KILL YOUR XBOX! --",1
Section "I understand the risks and & I want to continue"
{
Line "-- COULD KILL XBOX ! --",1
Item "4-1) Flash 1/2 TSOP 512K with D6-EjectFix",@273
Line "------------------------------------",2
Item "4-2) Flash 1/2 TSOP 512K with X2-4976.02",@274
Line "------------------------------------",2
Item "4-3) Flash 1/2 TSOP 512K with X2-4977",@275
Line "------------------------------------",2
Item "4-4) Flash 1/2 TSOP 512K with MS-3944",@276
Line "------------------------------------",2
Item "4-5) Flash 1/2 TSOP 512K with MS-4034",@277
Line "------------------------------------",2
Item "4-5) Flash 1/2 TSOP 512K with MS-4817.01",@278
Line "- Needs Both Bridge Points on MB!-",1
}
Line "- Read TSOP Tutorials First! -",1
}
Line "------------------------------------",2
Item "6) System Settings",@9
Line "------------------------------------",2
Item "7) Power Off Xbox",@10
}
[Action_70]
Info "Ready To Flash Full TSOP 1MB"
Info "With Evox D.6 EjectFix MultiVer"
Info "Once Complete the Xbox will self Reset"
Info "BIOS Write Enable points MUST be bridged"
Info "Unit Must be operating without a Mod Chip"
Warning "If Uncertain, Turn Off Xbox to Abort!"
flashbios "biosEvoXD6_EjectFix.bin"
[Action_71]
Info "Ready To Flash Full TSOP 1MB"
Info "With Xecuter2 4976.02 MultiVer IGR"
Info "Once Complete the Xbox will self Reset"
Info "BIOS Write Enable points MUST be bridged"
Info "Unit Must be operating without a Mod Chip"
Warning "If Uncertain, Turn Off Xbox to Abort!"
flashbios "biosX2_497602_MultiVer.bin"
[Action_72]
Info "Ready To Flash Full TSOP 1MB"
Info "With Xecuter2 4977 NROEF"
Info "Once Complete the Xbox will self Reset"
Info "BIOS Write Enable points MUST be bridged"
Info "Unit Must be operating without a Mod Chip"
Warning "If Uncertain, Turn Off Xbox to Abort!"
flashbios "biosX2_4977.bin"
[Action_73]
Info "Ready To Flash 1/2 TSOP 512K"
Info "With Evox D.6 EjectFix MultiVer"
Info "Once Complete the Xbox will self Reset"
Info "BIOS Write Enable points MUST be bridged"
Info "Unit Must be operating without a Mod Chip"
Warning "If Uncertain, Turn Off Xbox to Abort!"
flashbios "biosD6_EjectFix512.bin"
[Action_74]
Info "Ready To Flash 1/2 TSOP 512K"
Info "With Xecuter2 4976.02 MultiVer IGR"
Info "Once Complete the Xbox will self Reset"
Info "BIOS Write Enable points MUST be bridged"
Info "Unit Must be operating without a Mod Chip"
Warning "If Uncertain, Turn Off Xbox to Abort!"
flashbios "biosX2_497602_MultiVer512.bin"
[Action_75]
Info "Ready To Flash 1/2 TSOP 512K"
Info "With Xecuter2 4977 NROEF"
Info "Once Complete the Xbox will self Reset"
Info "BIOS Write Enable points MUST be bridged"
Info "Unit Must be operating without a Mod Chip"
Warning "If Uncertain, Turn Off Xbox to Abort!"
flashbios "biosX2_4977_512.bin"
[Action_76]
Info "Ready To Flash 1/2 TSOP 512K"
Info "With MS Original 3944"
Info "Once Complete the Xbox will self Reset"
Info "BIOS Write Enable points MUST be bridged"
Info "Unit Must be operating without a Mod Chip"
Warning "If Uncertain, Turn Off Xbox to Abort!"
flashbios "biosMS_3944_512.bin"
[Action_77]
Info "Ready To Flash 1/4 TSOP 512K"
Info "With MS Original 4034"
Info "Once Complete the Xbox will self Reset"
Info "BIOS Write Enable points MUST be bridged"
Info "Unit Must be operating without a Mod Chip"
Warning "If Uncertain, Turn Off Xbox to Abort!"
flashbios "biosMS_4034_512.bin"
[Action_78]
Info "Ready To Flash 1/2 TSOP 512K"
Info "With MS Original 4817.01"
Info "Once Complete the Xbox will self Reset"
Info "BIOS Write Enable points MUST be bridged"
Info "Unit Must be operating without a Mod Chip"
Warning "If Uncertain, Turn Off Xbox to Abort!"
flashbios "biosMS_4817-01_512.bin"
Post by: fearyaks on August 03, 2003, 10:52:00 AM
I was under the impression that you needed a specific bios to even run EvoX (the dashboard). Isn't this kind of a chicken-egg issue? Or will EvoX work on all types of bios'?
-I'm probably going to get myself an X-ecuter 2.2 Pro. -
Regardless, a good tutorial (not used it yet though).
Thanks!
Post by: Unreal7000 on August 05, 2003, 03:33:00 PM
Post by: dagretchen on August 06, 2003, 09:55:00 AM
Flash = 0x01d5,"XECUTER2",0x100000
should I include that?
Oh, and great tutorial man,
Post by: Unreal7000 on August 10, 2003, 07:28:00 AM
This post has been edited by Unreal7000: Aug 10 2003, 02:29 PM
Post by: pdexter on August 11, 2003, 10:19:00 PM
| QUOTE (dagretchen @ Aug 6 2003, 06:48 PM) |
| I've been searching through the forms, and I've got the impression that I can flash my bio from evox with either a 256, 512, or 1024 bin, (I'm useing xecuter 2.2 lite) is this true or must I make a 1024 .bin? Also I heard "DONT DO THIS WITH EVOLUTION X 1.8.3682 there is a bug, Use either 3285 or 3752", is this true? And finally someone said to include also Flash = 0x01d5,"XECUTER2",0x100000 should I include that? Oh, and great tutorial man, |
Yeah, that's correct about that version of evox not being able to flash bios' properly.
Aparently it was a fairly random problem (it worked for some, not for others).
Just make sure that you've got the latest version and you should be right!
Post by: noobiex2 on August 14, 2003, 06:05:00 PM
Thanks for the great tutorial
Post by: Unreal7000 on August 15, 2003, 09:17:00 AM
Post by: Good-vs-Evil on August 20, 2003, 05:42:00 PM
It worked for me, and now i've messed about withthe colours too
I have a x2.1 lite which has four banks. could i put a different bios on all 4 banks like evox and others etc. What would be the point and how could i use the or select the bios's?
Post by: Unreal7000 on August 20, 2003, 08:50:00 PM
This post has been edited by Unreal7000: Aug 21 2003, 03:50 AM
Post by: Good-vs-Evil on August 21, 2003, 04:32:00 AM
Thanx for the reply, i won't bother mucking around anymore, it works for me as is!
One thing i did notice: b4 i had the 4976 bios that came with my mod chip. Everything works perfectly. Including ghost recon island thunder. But since updating my bios to 4977 GR island thunder no longer loads. I've re-installed to my hdd, inc patches and repatched my self. basicly i've tried various methiods but i get black screen all the time. Its not too much of a problem coz i aint totally down with the game, But im just making it known this game no longer works with the updated bios. I will go back to my first bios and try the game again to see what happens.
Post by: moola on August 25, 2003, 11:54:00 PM
Many thanks
Post by: j051499 on August 26, 2003, 10:34:00 AM
I need a little help here with flashing my X2. I have an Xecuter 2.0 Lite. It came pre-flashed with X2 4973 1.0. I've searched the forums and read several tutorials, and near as I can tell, I'm the first person who has asked about the following problem.
When I try to flash the bios to 4977, my Xbox triple boots, followed by flashing red/green around the eject button. Here are the steps I've taken:
1) Remove X2 mod chip from mobo
2) Remove Flash jumper from mod chip
3) Replace mod chip on mobo and reconnect all the drives and power supplies
4) Turn on Xbox
5) That's it - as soon as I hit the power button, I get the triple boot followed by alternating red/green flashing light
FYI, I've tried putting the Flash jumper back on and removing just the Bios jumper, thinking maybe my X2 was mis-labeled somehow, but the Xbox does the same thing once I start it up - it triple boots, then flashes red/green. I've also tried removing BOTH jumpers - the Flash and Bios jumpers - and I get the same triple boot. And I've tried removing just the middle jumper, which disables the mod chip, and I get the expected error that says my Xbox needs servicing (b/c my HDD isn't locked).
When I put all the jumpers back on, the Xbox works perfectly - no problems starting it whatsoever, so I know I didn't fry the chip or the mobo or anything else. I can't believe I'm the only one who's had this problem, so if someone else has experienced it, can you give me your tips on how you finally got around the triple boot?
Thank You!
Post by: j051499 on August 26, 2003, 10:59:00 AM
Post by: bama51 on August 29, 2003, 06:29:00 AM
Section "Chameleon Mode 1",ID_Chameleon_Mode_1
{
Line "Mode 1 (4x256k)"
Item "Switch To TSOP (Disable Chameleon)",ID_Chameleon_Release_D0,ID_Full_Reboot
Item "Switch To Bank 0",ID_Chameleon_Bank_0,ID_Full_Reboot
Item "Switch To Bank 1",ID_Chameleon_Bank_1,ID_Full_Reboot
Item "Switch To Bank 2",ID_Chameleon_Bank_2,ID_Full_Reboot
Item "Switch To Bank 3",ID_Chameleon_Bank_3,ID_Full_Reboot
Line "-=*-*=-"
Item "Flash Bank 0",ID_Chameleon_Bank_0,ID_Flash_Bios
Item "Flash Bank 1",ID_Chameleon_Bank_1,ID_Flash_Bios
Item "Flash Bank 2",ID_Chameleon_Bank_2,ID_Flash_Bios
Item "Flash Bank 3",ID_Chameleon_Bank_3,ID_Flash_Bios
}
Please help if you can. I really want to flash my bios to something besides what I am running.
Post by: TIAGM3 on September 03, 2003, 11:37:00 PM
| QUOTE (nix2k @ Jul 15 2003, 11:16 PM) |
| -- Flash = 0x01d5,"AMD - Am29F080B",0x100000 As far as I know, anyone using X2 chips just need that line in their flash section. As for other chips, no idea, I use an X2.1 lite, and thats the line you need. |
This tutorial was tits!
Helped me out a lot! I had to read it like 5 times though 
Thanks!
Post by: ninja friend on September 07, 2003, 07:58:00 PM
The thought of flashing my bios horrified me. I have heard so many stories of people turning Xboxes into paperweights because of bad flashes.
After reading your thread, I finally got up the nerve to go ahead and update to 4977... and everything went smooth as can be. Your directions were very explicit, and you made it easy to get the job done. Hell, even a complete tool like me was able to flash the bios, complete with all sorts of unecessary things like ditching the trademark logo, and modding the various colors of the boot logo.
Thank you, thank you, thank you.
Post by: barbapapa5800 on September 10, 2003, 11:42:00 AM
i am getting the error "filesize to big" when trying to flash a 1024k bios ( 4977).
the problem is that i don't know what kind of chip is installed.
a had my xbox modded by someone who makes his own mod chips.
therefor i don't know how big the banks are.
can i try a 512k bios whitout the risk of fu***ng it up?
or how do i find out how big the banks are?
thnx
Post by: Unreal7000 on September 11, 2003, 05:44:00 PM
But yes 512K would be the next down. So I would assume that it would be ok to try. If you still get the same error try 256k.
This post has been edited by Unreal7000: Sep 12 2003, 12:45 AM
Post by: barbapapa5800 on September 12, 2003, 04:32:00 AM
i tryed 512 without result.then 256, that whas ok...
thnx for the reply...
Post by: elfey1 on September 12, 2003, 04:59:00 AM
Post by: op_ivy on September 14, 2003, 01:34:00 PM
however, now how do i go about re-flashing the bios if i cant get the xbox to boot with only 4 on?
Post by: Unreal7000 on September 14, 2003, 01:44:00 PM
Post by: op_ivy on September 15, 2003, 06:30:00 AM
Post by: Unreal7000 on September 16, 2003, 07:38:00 AM
Win9x/ME http://dwl.xbox-scen...flash/x2pro.zip
Post by: op_ivy on September 16, 2003, 05:22:00 PM
heres what i got
Post by: Unreal7000 on September 17, 2003, 03:06:00 PM
Post by: MrSelfDestruct on September 21, 2003, 03:27:00 PM
| QUOTE |
| So lets say you have a virgin 1MB X2 4976.02 BIOS, make sure the hash marks are identical (usually if the first 5 or 6 numbers match then your golden, but just make sure they all match). |
Post by: Unreal7000 on September 21, 2003, 03:34:00 PM
Post by: MikeF on October 07, 2003, 12:41:00 AM
Cheers
Post by: sexylinni on October 09, 2003, 05:54:00 AM
This has been a very valuable resource. I agree with 'mrselfdestruct' that the hash marks? bit is hard to understand . Would love you dumb it down for us computer illiterate.
Post by: 420warrior on November 13, 2003, 09:16:00 PM
Post by: andyd on November 20, 2003, 10:25:00 AM
| QUOTE (dink @ Jul 11 2003, 05:46 PM) |
| Great tutorial! I have spent many hours searching for something like this. Instead, I put together my evox.ini from various threads. As I recall, I had to add in the evox.ini, the type of flash chip, in order to flash it. I did not see it in your turtorial. Flash = 0x01d5,"AMD - Am29F080B",0x100000 Flash = 0x04d5,"FUJITSU - MBM29F080A",0x100000 Flash = 0xadd5,"Hynix - HY29F080",0x100000 Flash = 0x20f1,"ST - M29F080A",0x100000 Flash = 0xbf61,"SST - 49LF020",0x40000 |
Got two questions...
1. Where would I get the info for the flash part??? Or is there a chance that its in the ini already (I'm at work now so can't check)
2. So I'm planning on updating to 4979 tonight. Since its size is 256, would I place the same exact thing in the two banks of one of the sides? Then I can fill the other two with something that fits 512?? I just want to make sure I'm understanding this as I would like to avoid doing anything stupid.
Post by: adam71o on November 20, 2003, 04:05:00 PM
Any suggs?
Post by: heinrich on November 20, 2003, 04:21:00 PM
| QUOTE (adam71o @ Nov 20 2003, 07:58 PM) |
| I'm trying to flash my bios as well. I am running MxM, but I can run Evox as an app. When I DO run Evox and go to "Flash Bios" I am taken to a blank list, I can see the "highlighted file-bar" but theres no file listed there, and I can back out to the rest of the menu. Theres just NO bios listed when I hit "Flash Bios." Any suggs? |
Did you put the bios in the ./bios folder of where ever you have evox? So if you have evox in F:\apps\evox\ then you need to put your .bin's in F:\apps\evox\bios\
Post by: adam71o on November 20, 2003, 04:31:00 PM
Post by: Corspegrinder99 on December 11, 2003, 01:36:00 PM
Post by: khaoz on December 13, 2003, 05:10:00 AM
I am having some trouble flashing my xecuter 2.3 lite (v1.00 xbox). When I first finished soldering all the wires, and basicly finished all of the hardware procedures, the xbox would start up and ask me for the flash cd. I had found a tutorial somewhere to make the bios cd, and I got the bios from the modchip official website. After it had finished flashing, it kept asking to be flashed again after booting it (did not know this was supposed to happen for i had not seen this tutorial).
Anyway, after thinking this was not supposed to happen, i thought it was a problem with the bios, so as solution, i tried another bios, i forget which one, one of the top 2 (according to list order) found here: http://www.xbox-scene.com/software/software.php?page=legalbios
After flashing it with that bios, every time I boot my xbox, it turns on and off two times, then the eject button starts to flash green and red, and nothing really happens (you can here the xbox running, but drive wont eject or read any discs). I cannot re-flash my xbox because i cannot get to the screen when it asks me too.
Have I just f-ed up my modchip? The xbox works fine when the modchip is turned off. Do you think it has anything to do with the LPC or Ground? I really need help!!
!!! !!!Post by: Unreal7000 on December 13, 2003, 09:47:00 PM
Post by: khaoz on December 14, 2003, 05:34:00 AM
Post by: Unreal7000 on December 14, 2003, 08:03:00 PM
Post by: bakin1 on December 16, 2003, 11:29:00 AM
Post by: scorpionking77 on December 17, 2003, 06:54:00 AM
Post by: mopflash on December 21, 2003, 12:37:00 AM
I am running a Xecuter2 chip on a xbox v1.0 with no extra hardrive installed.
Oh yeh whats a bios for the xbox do anywayz
Post by: ViolentDave on December 21, 2003, 04:37:00 PM
Post by: phizz on December 22, 2003, 03:01:00 AM
Iam a little confused whats the exploit method of modding?
Post by: NeOnRaBbIt on December 29, 2003, 12:54:00 PM
hey unreal thanks for the guide i edited the 4979.67 bios an i got this awsome startup with red xbox and a blue x it looks sweet!! plus a red LED...wish it was brighter though...
by the way...i think the xbox does modify the fan speed...through xbtool i had it at 70 but wen i checked in that lil program called FanThing it sed it was set at 35...maybe wen it gets to hot the fan increases??