Post by: skorchir on February 09, 2004, 11:09:00 AM
So you had a bad experience with avalaunch.. mostly due to video mode switching
Here is how you can fix it according to your Symptoms
NOT FOR PEOPLE WITH SOFTMODDED XBOX'S. IF YOUR XBOX IS SOFTMODDED THEN YOU GOT OTHER PROBLEMS WHICH ONLY A MODCHIP CAN FIX
Symptom 1:
xbox Turns On and Freezes at the Big X Logo Or/And Error Code Displays
Symptom 2:
Xbox Turns On Video Is Scrambled And Flickering. Or Video is Incorrect.
Symptom 3:
Xbox Turns On NO VIDEO, No Sound And Flashing RED
Symptom 4:
Power On/Off 3x FRAG, No Video, No Sound
SOLUTIONS:
Symptom 1:
Create or Use a Boot Disk And And Repair Your C:, Dashboard, XML. This is Dashboard Related due to an error in configuration, Or is unable to locate dashboard.
Symptom 2:
Your Xbox is Set to a Video Setting That Your TV Does NOT Support. Try booting pressing and holding both thumbsticks. If this does not fix it then Get a Hold of "Enigmah Video Switcher" found in the usual places, make a boot disk with it. When its loaded Press "A" for PAL or Press "B" for NTSC. Then Reboot Your Video should work again
Symptom 3:
Ok So you are sitting In This Corner.. Ouch :( Never Fear It Is Fixable Very Easily with the right stuff. You will require a mod chip and programmer or some way of programming a mod chip to go on.
Case 1> You Have a backup of your eeprom. Excellent you can pat yourself on the back for intelligence :D what your need is Eeprom Recovery Package 1. This contains a Patched Cromwell bios with a program called AddEeprom. Get your eeprom backup and use Addeeprom to insert it into the cromwell binary. Flash this bios to your modchip and boot it up. It will Eject the CD-Tray and Your eeprom will be restored! If it didnt work the first time boot it again, or make sure you did everything correct.
IF YOu ARE USING THE ORIGINAL HARD DRIVE THAT HAS NEVER BEEN UNLOCKED AND DONT HAVE A EEPROM BACKUP. The Hard Drive is pretty much useless now. its probly time for you to upgrade to a bigger drive.
Case 2> You DO Not Have a backup of your eeprom.. SHAME ON YOU! But Never Fear I have supplied a EEProm for your Needs. If you Have a NTSC System get EEprom Recovery Package 2. If you have a PAL System you need EEprom Recovery Package 3. Flash This Version of Cromwell To Your Mod Chip and Boot Your System. Your System should now function Again! Great!.
Other Info>
Now you may have a problem with unable to unlock Hard Drive if your hard drive was locked If this is the Case try the password "TEAMASSEMBLY". Hopefully you wont have this problem and all is good. Package 2 and Package 3 Have the HDD Password preset to TEAMASSEMBLY.
Symptom 4:
Something is preventing your bios from loading. Possibilites: MOD Chip is loose or any other mod chip related problem, Your BIOS is HOSED (Due To Improper Flashing of BIOS) Sorry Avalaunch does not support this or you found a fatal Easter Egg. Either Reflash your mod chip with programmer, or Fix TSOP with Proper Mod Chip depending on your system.
I Hope this has helped you a lot and i hope this hasnt scarred your for life but for the future make sure to keep eeprom backups and it would be good to have a mod chip with programmer this way your arnt stuck in the water.
EEprom Recovery Package 1
http://skorchir.homelinux.org/EEPROM_RECOVERY_PACKAGE_1.rar
EEprom Recovery Package 2
http://skorchir.homelinux.org/EEPROM_RECOVERY_PACKAGE_2.rar
EEprom Recovery Package 3
http://skorchir.homelinux.org/EEPROM_RECOVERY_PACKAGE_3rar
I would also like to add that i did not write these programs/bios i am simply supplying it for the needy. I would like to give great credit to the writter of these tools but i cant remember as of where i obtained them. ;)
Very Handy Though
I Have one bank dedicated to this bios for just these situations.
Also Remember Avalaunch being in Alpha/Beta Stages you are a Tester! If you fuck your xbox it is not entirly the fault of the developers. They do their very best to obtain quality. I like to give great appreciation to the avalaunch team for their hard work and their great dashboard. BTW If you need any more pre-release testers you can count me in :)
Please post any success stories :)
Thx
This post has been edited by skorchir: Feb 10 2004, 04:44 AM
Post by: Zappo on February 09, 2004, 02:32:00 PM
Does Avalaunch - like often statet - save the EEPROM values on every boot, so I may gladly recover my EEPROM from this backup.
And second, does the X2 4977 bios really boot without EEPROM settings?
This could fix the problem much easier:
Flashing X2 4977 on another LPC modded XBOX, transfer the LPC to the broken XBOX, boot with both thumb-buttons pressed to restore old EEPROM settings.
And a third: Am I right?
Post by: Itzgizz on February 09, 2004, 03:12:00 PM
It doesn't support 1.4/1.5 boxes due to the fact that it uses 1.24dev. If anyone has a fix on a newer vserion, would be GREATLY appriciated.
the source for the changes to cromwell are HERE just dunno how to use it to patch up a newer version (if possible).
This post has been edited by Itzgizz: Feb 9 2004, 11:15 PM
Post by: daweeze02 on February 09, 2004, 03:55:00 PM
anyone getting this error i have everything in the same directory too.
Post by: skorchir on February 09, 2004, 08:48:00 PM
| QUOTE |
| does the X2 4977 bios really boot without EEPROM settings? |
Apparantly it does and so do debug bios's only problem is this wont help you *fix* the problem since you cant flash your eeprom with them. it seems it just doesnt work
| QUOTE |
| It doesn't support 1.4/1.5 boxes due to the fact that it uses 1.24dev. If anyone has a fix on a newer vserion, would be GREATLY appriciated |
I guess it doesnt ? i dont have a 1.4/5 here to play with
| QUOTE |
| Cannot find bootloader cromwell-patched.bin |
hmm wierd.. It seems addeeprom cant find that filename ?
Post by: Zappo on February 09, 2004, 09:28:00 PM
| QUOTE |
| Cannot find bootloader cromwell-patched.bin |
Try to rename it to a 8.3 filename, e. g. cromwell.bin
| QUOTE |
| Apparantly it does and so do debug bios's only problem is this wont help you *fix* the problem since you cant flash your eeprom with them. it seems it just doesnt work |
But Avalaunch can - as often stated here - restore the previous EEPROM, when both thumbsticks are pressed on booting. I just haven't heared, if this is in fact the behavior of Avalaunch... can you confirm this?
And if it doesn't, when the box has booted, is there another possibility to restore the EEPROM via a tool, e. g. FlashFXP?
This post has been edited by Zappo: Feb 10 2004, 05:31 AM
Post by: firefli on February 09, 2004, 09:37:00 PM
Post by: Zappo on February 09, 2004, 09:59:00 PM
This might help, if the XBOX can boot with a X2 4977 bios. So even the V.1.5 XBOXes can be recovered in a simple way - so I think.
I really do not like to get a 200,- EUR paperweight...
BTW: Can anyone describe, how and with which tool to unlock the XBOX HDD with the TEAMASSEMBLY password via PC?
Post by: Zappo on February 09, 2004, 10:31:00 PM
I've just tested the X2 4977 bios, but the box wont boot: When pushing and holding the power button to turn on the Aladin Advance chip, the eject-led is getting green for a second, then the box turns off.
Is there a special debug-version of the 4977 available?
Post by: MosaX on February 09, 2004, 11:19:00 PM
Just to be sure, did the following event in any way change my original bios? If so, may if affect my ability to run XBOX Live or unlock my harddisc?--
I autoupdated my Avalaunch to v0.48.55 and looked around, by accident happened to press SELECT in Settings:Hardware Info. A dialog "PAL 60" showed on screen. I wasn't sure but I realized something might have changed but didn't dare press SELECT again since I imagined it could then be changing into NTSC mode. I rebooted, tested with a number of games and programs and all worked except XBMP and XBMC which both just wouldn't load. Eventually I went back to Avalaunch and dared cycle back to "PAL I". Now XMBP and XBMC worked again.
I have a XBOX 1.1 PAL, PC-BioXX w/ X2 4980, 120 GB HD Locked.
(A good theme when designing an application is to always "design for errors", that is a function such as video switching SHOULD have one or even two confirmation dialogs or sort.)
Post by: dno on February 09, 2004, 11:48:00 PM
;)
Post by: Zappo on February 09, 2004, 11:55:00 PM
This post doesn't really concern to this topic, does it?
------
Back to topic: I now tried the cromwell-patched bios on my XBOX, but same as the 4977 happend, XBOX is powerd off after a second.
Now I might understand Itzgizz posting: This bios versions don't run on the V.1.5 machines, I didn't get this before.
So what now? Is there a bios to get which works on the 1.4/1.5 XBOXes and boots with damaged EEPROM?
Maybe Team Avalaunch can connect to the Xecuter Team for a favour?
It's not only me, many other have corrupted their XBOX with Avalaunch, this may really save some money...
Post by: Itzgizz on February 10, 2004, 12:01:00 AM
Post by: phily on February 10, 2004, 01:21:00 AM
I had the problem with no video and a red flashing screen.
This is what i did.
Got a lend of a xbox with a working modchip.
Used XBTool to edit Xecuter2.Build.4977 to boot with the dashboard of your choice (i booted directly to the old installation of evox, never deleted it)
Flashed it with Xecuter2.Build.4977 which i had edited.
I remembered I played with a backup tool awhile ago and didnt delete the files it made
so i knew i could go back to the old setting!Placed the working modchip with the now X2.4977 bios into my dead xbox, kept my fingers crossed and boom! it booted ignoring the fecked eeprom! wahoo!
I got the backup of my eeprom and placed it into the root directory of the C drive on the xbox, named it eeprom.bin
Used an app called eepromagic v0.01, it first backups the existing eeprom and then it allowed me to write the backup i had placed on the C drive on the xbox.
Rebooted after taking out the mod and the machine booted and i updated avalaunch with the latest version which doesnt have the options to mess the system up
Mental Note: Dont play with options that might feck up the xbox, just leave alone and only change them if I need too.
Post by: GoD][Zvert on February 10, 2004, 02:35:00 AM
)i flashed the patched cromwell !! i had a backup (or so i thought somewhere, or at least i had a file called Eeprom in my xbox backup folder...) but nothing happend when flashing that
so i tried the one u supplied... it did the trick but now i can't get passed the Error 6 !!
i am not a total noob at this but all this is kinda new to me so could u explain how to let my xbox Unlock my drive now ???
oh yea i am using a 1.0 with MAtrix chip,
i got a new 80gb and the original 8gb
Post by: Pandoriaantje on February 10, 2004, 07:29:00 AM
| QUOTE (skorchir @ Feb 9 2004, 08:02 PM) |
| ... Symptom 4: Power On/Off 3x FRAG, No Video, No Sound SOLUTIONS: ... Symptom 4: Something is preventing your bios from loading. Possibilites: MOD Chip is loose or any other mod chip related problem, Your BIOS is HOSED (Due To Improper Flashing of BIOS) Sorry Avalaunch does not support this or you found a fatal Easter Egg. Either Reflash your mod chip with programmer, or Fix TSOP with Proper Mod Chip depending on your system. .... Thx |
had that problem twice now.
i have a x2 pro chip soldered myself and it's working perfectly (has been for about 1-2 years).
so it's kinde strange that the chip would be malfunctioning just when i switched to avadash...
i like it, but i'm still blaming it though.
using the eeprom flashbios has helped me so far (does require me to play around with booting methods, eject button, power button, video cable in, cable out) but i've managed to fix it on both occasions by reflashing my eeprom.
last time i didn't even change videomode settings. just played around with a trainer patched GTA vice city. doing a igr left me at a black screen. Pressing eject rebooted the xbox but after a powerdown it wouldn't boot anymore...
Post by: Heet on February 10, 2004, 07:33:00 AM
I did fix a red flashing 1.4 with the eeprom fix as far as I know. I could be wrong but if I remember correctly it was a 1.4. The version of the box should not matter here(eeprom fix), but I guess it would make sense that 4977 wouldnt work on a newer box.
If you find that the eeprom fix didnt work for you dont worry, it just means your using the wrong version eeprom. In other words, if you use a 1.0 eeprom and flash using cromwell-patched.bin and your still getting blinking red, it means you need a 1.1 eeprom!!
Also a sidenote, Ive had countless people in IRC coming to me and saying that they are getting "eeprom encrypted region invalid" in config magic. If your getting this it may be because YOUR USING THE WRONG VERSION OF CONFIG MAGIC!! Use the final build that supports 1.0 AND 1.1 eeproms and all will be better. Have a great day!!
Post by: thexboxking on February 10, 2004, 11:41:00 AM
Post by: NghtShd on February 10, 2004, 01:47:00 PM
| QUOTE (thexboxking @ Feb 10 2004, 04:41 PM) |
| please help i have tryed all but my drive wont unlock. i need to get this back up so i can finish a ps2 emulator. PLEASE PEOPLE HELP ME OUT. i do love the look and feel of ava but i need to get this fixed asap |
Someone please help this guy so he can finish his PS2 emulator. Between dating Britney Spears, being The President of Moldavia and his astronaut duties, I'm sure he doesn't have the time to figure this out. I wouldn't want to have to wait until he gets back from Mars. Maybe he'll share some of his pictures of sasquach with you in return.
Post by: leftyfb on February 10, 2004, 01:59:00 PM
| QUOTE (thexboxking @ Feb 10 2004, 04:41 PM) |
| please help i have tryed all but my drive wont unlock. i need to get this back up so i can finish a ps2 emulator. PLEASE PEOPLE HELP ME OUT. i do love the look and feel of ava but i need to get this fixed asap |
LOL
nuff said
Post by: geniusalz on February 10, 2004, 02:14:00 PM
| QUOTE (thexboxking @ Feb 10 2004, 04:41 PM) |
| please help i have tryed all but my drive wont unlock. i need to get this back up so i can finish a ps2 emulator. PLEASE PEOPLE HELP ME OUT. i do love the look and feel of ava but i need to get this fixed asap |
Good luck with the emulator
Post by: leftyfb on February 10, 2004, 04:18:00 PM
Post by: thexboxking on February 10, 2004, 07:50:00 PM
and the port is no where even close to being done . just thought id give myself something to try since all the good stuff has already been done.
And to all those people hats off to you. YOU GUY'S ROCK AND KEEP IT COMING
Post by: skorchir on February 10, 2004, 08:18:00 PM
http://dwl.xbox-scen...einfo-beta2.zip
this is great for creating and editting eeproms, serial #'s, video modes, region, etc..
Post by: Zappo on February 10, 2004, 09:19:00 PM
It's a part of this PDF:
http://warlock-xbox.....de/XBOXFAQ.zip
The needed tools can be downloaded from xbox-scene.com
A tip from me: When connecting the xbox-hdd to the pc, use bios-setting for hdd "none", otherwise it may be, that bevore booting anything the pc asks for the hdd-key - and there TEAMASSEMBLY will not work. So disable any hhd in the bios and boot from a floppy. Anything else is in the tut.
Post by: art408 on February 10, 2004, 10:38:00 PM
I'm out of ideas
, anything else before I buy a MOD chip? Can I revive the old BIOS then remove chip, or am I forced to use the chip permanently?
Thanks in advance.
Post by: nimbles on February 11, 2004, 01:57:00 AM
| QUOTE (phily @ Feb 10 2004, 11:21 AM) |
| Used XBTool to edit Xecuter2.Build.4977 to boot with the dashboard of your choice (i booted directly to the old installation of evox, never deleted it) Flashed it with Xecuter2.Build.4977 which i had edited. I remembered I played with a backup tool awhile ago and didnt delete the files it made so i knew i could go back to the old setting!Placed the working modchip with the now X2.4977 bios into my dead xbox, kept my fingers crossed and boom! it booted ignoring the fecked eeprom! wahoo! |
Hey philly- is this the bog standard x2.4977 bios- didn't actually have the eeprom problem but switched down from x2.4981, edited it (booting to F:/dash/avalaunch/).
Asked around on teamxcuter forum and irc channel and they said it it needs the eeprom- just wondering whether you had a debug version (which i didn't see on xbins) or edited the standard one- with some tool?
Flashed my cheapmod back to 4981, assuming that the 4977 rumours weren't true. But if you managed to do it i guess i'll be putting the 4977 bios back in- naturally have backups of the eeprom and other things generated by evox.
Post by: redgob on February 11, 2004, 04:38:00 AM
Post by: skorchir on February 11, 2004, 05:48:00 AM
| QUOTE (amirxbox @ Feb 11 2004, 04:47 AM) |
| I had Symptom 3, after reprogram bios to 4977 have now Symptom 4. xbox version 1.0. What can i do?? please help meeeeeeee save my box!!!! |
hmmz 4977 should boot on a 1.0 no problem. You sure its a 1.0? Also some people say it works some say it doesnt. i havent tested 4977 with a toast eeprom myself. Why not try package 3? use the cromwell to reflash a good eeprom
Post by: PhReaK on February 11, 2004, 06:30:00 AM
| QUOTE (redgob @ Feb 11 2004, 02:38 PM) |
| Yes: use another modded xbox and swap the mod after boot in order to flash it. |
the only other modded box i know is modded with an Xbit and my x2l is installed with wires... guess i'm stuck then...
Post by: der_ray on February 11, 2004, 08:32:00 AM
any ideas why?
Post by: amirxbox on February 11, 2004, 08:39:00 AM
| QUOTE (skorchir @ Feb 11 2004, 04:48 PM) |
| hmmz 4977 should boot on a 1.0 no problem. You sure its a 1.0? Also some people say it works some say it doesnt. i havent tested 4977 with a toast eeprom myself. Why not try package 3? use the cromwell to reflash a good eeprom |
My mod is 256K so if i will flash it with the recovery kit i could'nt reflash it.
Allso i can't understand why i get #4 and before reprogram my bios #3
and yeah i'm sure it 1.0 box because 4974 and 4977 and evox 2.2 worked for me long time ago.
Post by: Itzgizz on February 11, 2004, 10:17:00 AM
| QUOTE |
| i have a 1.5 with xbit and when I boot my xbox i have no picture, no sound and the LED flashes red... The Cromwell-Bios didn't work for me any ideas why? |
Did you not read this thread before posting? The "cromwell-patched" does NOT work on 1.4/1.5. You have a paperweight untill a solution arises.
Post by: skorchir on February 11, 2004, 03:04:00 PM
its not easy, not hard, but not impossible, but still risky
I have not tested this but im am almost 100% certain this will work
What You Will Need: !
Another MODDED Xbox 1.0 - 1.3 With a spare bank
SOLDERING SKILLS
A Soldering Iron
A EEprom Image from a 1.4/1.5 System
Cromwell Eeprom Reflash Bios Kit (Package 1)
Step 1> CREATE A EEPROM BACKUP OF THE MODDED SYSTEM AND UNLOCK HARD DRIVE (Perferrably with Config Magic)
Step 2> Create a Cromwell bios image using the 1.4/1.5 eeprom
Step 3> Flash to a bank on the modded system. *DO NOT BOOT THIS IMAGE YET OR ELSE YOU WILL HAVE TWO FUBARD XBOX's*
Step 4> Desolder the eeprom from the broken xbox
Step 5> Desolder the eeprom from the working modded xbox
Step 6> Solder the bad eeprom into the other system
Step 7> BOOT CROMWELL EEPROM FLASHER
Step 8> Eeprom should be programmed now. Desolder it and solder it back into the other system
Step 9> Boot up both systems after re-installing eeproms and check. *MAKE SURE NOT TO BOOT THE CROMWELL BIOS OR YOU WILL HAVE ANOTHER PROBLEM*
Good luck. if you try this lemme know how it works out
Here is a picture of the EEPROM Circled in Orange
Post by: Zappo on February 11, 2004, 11:53:00 PM
That's really a nice idea, I come up to step 7:
Just to test, I reprogrammed the EEPROM from my V.1.5 in a V.1.1 with an V.1.1 EEPROM and to this step it works!
I did not try to flash with a 1.5 EEPROM, because
1st: I still get none (but maybe this afternoon)
2nd: I don't know, if EEPMOD (from tools-section) does support V.1.5 EEPROMs
So before I flash it and solder it back, I would like to get some info, if EEPMOD or LifeInfo supports V.1.5 EEPROM values, because I want to have my old serial no.
In this moment, I do steps 8 and 9, I give you immediate infos about.
I forgott: I don't want to flash another mod-chip with a second cromwell-eeprom-bios, so I remembered, that ConfigMagic can restore EEPROMs to.
So it should be possible to copy the V.1.5 EEPROM to E: of the V.1.1 XBOX, then let ConfigMagic load the EEPROM and then shut down the box and solder the EEPROM-chip back to the V.1.5.
What do you think?
But to be true: I don't understand this four EEPROM menus in Config Magic:
Load XBOX EEPROM
Load XBOX EEPROM from .BIN File
Build XBOX EEPROM from .CFG File
Update XBOX EEPROM
Can anyone explain (without guessing), what this menus do?
Post by: unleashx on February 12, 2004, 12:07:00 AM
Load XBOX EEPROM from .BIN File -Reads EEPROM from a .Bin file (your backup)
Build XBOX EEPROM from .CFG File --Reads EEPROM from your config file, if you happened to edit it with the right values.
Update XBOX EEPROM -Writes whatever values it holds in memory back to the EEPROM. You do this after editing your EEPROM on the fly. Your HD must be unlocked for it to succeed.
You can restore your orig SN by editing on the fly.
Post by: Zappo on February 12, 2004, 12:24:00 AM
| QUOTE |
| Load XBOX EEPROM -Reads EEPROM from the Xbox |
From where to where? Not the HDD to EEPROM?
| QUOTE |
| Load XBOX EEPROM from .BIN File -Reads EEPROM from a .Bin file (your backup) |
This seems the same to me as the first one... but if I do so (with the previously saved EEPROM by "create Backup Files") all values on the screen are blank or zero (I'm still working on the V1.1 xbox!):
| QUOTE |
| Build XBOX EEPROM from .CFG File --Reads EEPROM from your config file, if you happened to edit it with the right values. |
Same as above...
???
Post by: unleashx on February 12, 2004, 12:44:00 AM
| QUOTE | ||
From where to where? Not the HDD to EEPROM? |
It reads the values from the EEPROM chip and displays it on screen. It isn't save to anywhere yet, it just read it. You can't use this since yours is hosed.
| QUOTE | ||
This seems the same to me as the first one... but if I do so (with the previously saved EEPROM by "create Backup Files") all values on the screen are blank or zero (I'm still working on the V1.1 xbox!): |
You must have created a backup previously and the location should be set in the ConfigMagic.ini.
Taken from the said file above:
| QUOTE |
| [INPUT_FILES] #NOTE ONLY Drives C, D, E, F are supported !! #Remember that D is always the normal relative App Path !! EEPROMBinFile = "D:\data\eeprom.bin" EEPROMCfgFile = "D:\data\eeprom.cfg" |
The third one will read values from "eeprom.cfg". This file should contain everything, as if it was the .bin file.
After you edited some of the values on screen, then you can use the "Update XBOX EEPROM" option to write this back to the EEPROM chip.
Post by: redgob on February 12, 2004, 12:50:00 AM
Post by: Zappo on February 12, 2004, 03:40:00 AM
Post by: Zappo on February 12, 2004, 10:18:00 AM
My big thanks goes to Skorchir and UnleashX!
To the first for his great idea, to the second for immediate help with Config Magic.
I will start a new topic, telling everyone an how-to - with © to skorchir
New topic titel to search for: Reflash an V.1.5 EEPROM with a V.1.1 XBOX
Post by: skorchir on February 12, 2004, 12:34:00 PM
| QUOTE |
| New topic titel to search for: Reflash an V.1.5 EEPROM with a V.1.1 XBOX |
this should actually work with any xbox thats not 1.4/1.5
Good job!
Post by: Zappo on February 12, 2004, 02:01:00 PM
Post by: Hansi on March 09, 2004, 05:24:00 AM
This is a quite easy way to do it, but you need a SmartXX or Xenium modchip and a working XBOX with a compatible EEPROM.
1: Fit the modchip in the working XBOX and backup the EEPROM to the chip using the chips built-in menu system
2: Fit the modchip in the "broken" XBOX and restore the EEPROM from the image stored in the chip
3: Use Config magic to write another EEPROM.BIN (use one from the recovery packages in the beginning of this thread) to the fixed xbox, this is only neccesary if you want to use the first XBOX on LIVE.
4: Backup the EEPROM to the chip again (If you want to keep the chip to fix other xboxes in the future, I know I want to have that chip around for the next time)
If you were lucky enough to have a hard disc that was locked using evo-x dashboard or config magic, find and download ATAPWD.EXE and put it on a bootable floppy. Make sure you know where on the IDE chain you put your hard disc (if it is primary master, primary slave, secondary master, secondary slave).
Unlock HD steps:
1: Start atapwd
2: Choose the correct disc, press F5 to rescan if it does not appear. PM=primary master, PS=primary slave, SM=secondary master, SS=secondary slave.
3: Choose "Unlock using master password" and enter TEAMASSEMBLY
4: Choose "Disable using master password" and enter TEAMASSEMBLY
Good Luck!
Post by: Rainy on March 10, 2004, 03:00:00 AM
Post by: Noutaja on March 10, 2004, 01:17:00 PM
| QUOTE |
I have flashed my x2.3b lite chip with the cromwell-patched bios with my eeprom imbeded but its flashed the whole chip? bank 1 and 2 are displaying the linux boot screen asking for a boot cd? is there a way to restore my bios from this boot screen? |
http://www.xbox-scen...s/x2p-evox.php (step 3.)
Using nero: No Multisession, ISO Level 1, Format Mode 1, ISO 9660, (NO) Joliet, Finalize CD, Disc-At-Once.
both bin's are in root directory in CD
Post by: zcdohl on March 14, 2004, 06:55:00 AM
Post by: skorchir on March 14, 2004, 07:40:00 AM
what happens when you try using the cromwell patched bios?
Post by: Noutaja on March 14, 2004, 03:43:00 PM
| QUOTE |
| i have toaster eeprom, using cromwell-patched useless on my x2.3 lite, Using x4977 bios, xbox boot fine but can not write backup eeprom, using configmagic final find error "Invalid xbox version specified". Using x4981 embed eeprom xbox boot fine too but same x4977 can't write backup eeprom. After using all eeprom program writer, write sucessfull but on reboot back to toaster eeprom.. Any suggestion because i don't know what to do ? |
I used x4977 bios and eepromagic v0.01
Edit: Oh... configmagic gave same error me too. I'w been fixed two eeprom's with this method.
Post by: skorchir on March 14, 2004, 07:10:00 PM
Post by: zcdohl on March 14, 2004, 11:02:00 PM
Post by: nimbles on March 17, 2004, 01:54:00 PM
I I've got addeeprom.exe, the cromwell-patched.bin, and my backed up eeprom in the same folder.
I double click on the exe file and a cmd screen very briefly flashes up on the screen- is that it? Should there be some sort of confirmation?
thanks guys
Post by: Noutaja on March 17, 2004, 08:58:00 PM
Copy your addeeprom.exe to c:\temp (or somewhere else near root directory), so you don't have to write all paths IN COMMAND PROMT. Also your bios (256k) and eeprom.bin. Now klick start-> run... and type "cmd". Do I have to write DOS commands how to move in directories???? (I don't thinkso). Go there where you copyed files and type "addeeprom", now you will get instruction how to do use this program.
Hey, btw. Don't be sorry for draging up this TOP topic.
Post by: nimbles on March 18, 2004, 01:04:00 AM
Post by: keeborts on March 18, 2004, 09:01:00 AM
Post by: skorchir on March 18, 2004, 09:49:00 AM
| QUOTE |
| skorchir, i found the problem, it's from xecuter 2.3 lite who do not want boot with cromwell patched so i try using smartxx its boot fine...i found message that eeprom restore ...Failed....any suggestion ? |
thats strange that it wont boot it should as long as it isnt a 1.4+ as for an eeprom restore failing i cant see why this would happen unless there is no eeprom embedded or is corrupt ?. having a smartxx you should be able to restore an eeprom from within the chip. if you can get your hands on another xbox of same version you can install the smartxx, take a backup of the eeprom and resotre it to yours then re-write or edit it with config magic.
| QUOTE |
| for symptom 1 , all i did was upload mp3s into my background music folder, rebooted my xbox, then now it just stays at the xbox logo screen. and also about bootdisks, i've been looking but have been unable to find one for xbox. perhaps some can direct me somewhere, pm me if ya have to. i just wannafix my xbox |
well i cant really point you to a disk but it is possible for you to make one. The easiest thing for you might be to get a copy of slayers hdd loader. i dont know exactly where you can find it. But there should be a number of tutorials on making a boot disk. Try hitting eject at the frozen X it should reboot and sometimes it boots in. I found this trick to work with older versions of avalaunch that liked to lock up on boot.
Post by: nimbles on March 18, 2004, 10:01:00 AM
if xecuter is hanging but there is no abnormal flashing led's I think you may be able to- don't use avalaunch as it may access the hard drvie settings, get a copy of evox, and the ini file- possibly put in a large (50~100mb) dummy file, iso it up with qwix or another iso tool, burn the iso to a cd/dvd-rw and pop that in the drive- you'll then have the ability to ftp provided you edit the evox.ini to suit your ip config, and then you should be able to rectify the solution
Post by: keeborts on March 18, 2004, 10:11:00 AM
| QUOTE (nimbles @ Mar 18 2004, 08:01 PM) |
| keeborts- can you boot to the dvdrom drive? |
no it just stays at this screen, lets se eif i can re-make it here
X
XBOX
Xecutor
know wut i mean?
Post by: zcdohl on March 18, 2004, 06:37:00 PM
| QUOTE (skorchir @ Mar 18 2004, 07:49 PM) |
| thats strange that it wont boot it should as long as it isnt a 1.4+ as for an eeprom restore failing i cant see why this would happen unless there is no eeprom embedded or is corrupt ?. having a smartxx you should be able to restore an eeprom from within the chip. if you can get your hands on another xbox of same version you can install the smartxx, take a backup of the eeprom and resotre it to yours then re-write or edit it with config magic. |
skorchir,i try using cromwell-pacthed with smartxx its says "EEPROM Flashed failed". then i try using smartxx eeprom freature as you recomended to me, but everytime i try to "restore eeprom from Flash" it's hang...and i must reboot xbox to make smartxx run again
Something wrong with my mobo or this is normal ? it's like eeprom chip on write protect mode...
| QUOTE (keeborts) |
| no it just stays at this screen, lets se eif i can re-make it here X XBOX Xecutor know wut i mean? |
keeborts, my friends have this problem too, but he managed to fix it with slayer 1.8 cd. Just boot your xbox with slayers 1.8 disc and using configmagic to restore eeprom. I hope this can help you..good luck
Post by: keeborts on March 18, 2004, 07:47:00 PM
Post by: Froggie on March 24, 2004, 10:13:00 PM
Post by: Noutaja on March 25, 2004, 09:01:00 PM
| QUOTE |
| Anyone who has a mirror of the Recovery v.3 package? Cause the urls seem dead and I really need to fix my eeprom. |
So, you have allready package 1??. Now get this http://dwl.xbox-scen...einfo-beta2.zip Then you have all what you need. (I assume you dont have eeprom backup, when asking package 3)
Post by: PantherNO on March 30, 2004, 06:53:00 AM
I downoaded XECUTER v4981.
Used XBtool to embed eeprom in kelner.
Before embeded eeprom i changed it to a backup i had.
Flashed my Xecuter 2.3b, and wolla.
Post by: crzdmniac on June 22, 2004, 11:43:00 PM
Post by: Noutaja on June 23, 2004, 02:25:00 AM
| QUOTE |
| A sipel sulution for symptom 3 for xbox v1.4/1.5 I downoaded XECUTER v4981. Used XBtool to embed eeprom in kelner. Before embeded eeprom i changed it to a backup i had. Flashed my Xecuter 2.3b, and wolla. |
when you got Xbox to run. Flash eeprom with EEPROMagic V0.01 Beta.
*EDIT* I did that when XBtool 1.0.22 does not come out yet, soldering eeprom from Xbox 1.4 to 1.3 and using X2 4977. Flash, re-solder, ... After 24h current XBtool released.
Post by: Inuyasha152 on September 29, 2004, 11:20:00 PM
First off, I messed up my xbox when I i messed with the settings in avalaunch, then I came accross this. Well my symptoms were #2 and i followed the directions, when I loded it up I came to a weird screen and it said it flashed my eeprom succesfully then it said my HDD was locked (I didnt know I had to unlock it!!!) Now I cant get into avalaunch to unlock my hard drive, this is a brand new 80 gig hard drive and it cost me like 90 bucks! I dont want to have to return it, please if someone could help me I would GREATLY appreciate it!!!! I have an X-Chip and my xbox is a 1.0!
Please ANY help is GREATLY appreciated, oh and the error message I get is Number 06 when I try to load avalaunch!!!
-Vic
Post by: Inuyasha152 on September 30, 2004, 01:58:00 AM
Post by: pluey on October 08, 2004, 08:07:00 PM
Just one final step - when bios flashes - it gets too 100% and then gives following error:
'Error at location 00000H!'
What do I need to do to get past this last stage?
Post by: Gabman\ on October 14, 2004, 10:39:00 AM
As I can understand from this thread you can save it my flashing your modcip with the recover package 3 that you can download. Stupid as I am, I dont have a backup of my own eeprom.bin file.
But I use the Aladdin XT advance lite, and I dont think its possible to flash the bios without the xbox being operational. Am I right??
Is my xbox doomed because I have this crappy modchip ...
Hope someone has time to reply on this.....
Post by: TRIaXOR on October 20, 2004, 10:14:00 AM
using Config Magic I accidently screwed up the EEPROM (bloody dangerous tool that) and got Symptom 3 (Flashing red, no sound or picture) Luckily I had a Backed up EEPROM (using Evolution X) which was on my PC and my HDD was Unlocked (80GB Maxtor), the question was Like Gabman's how the hell was I gonna fix my XBOX 
After much scrutiny of the net (been thru LOADS of forums etc..) I came up with this solution..
Get a Mates Modded XBOX (your gonna need this to flash your BIOS)
Get XBTOOL and dump your backed up "eeprom bin" into "patch data"
a copy of Evox's M7 Bios (from the usual sources
)then embed your eeprom into EvoX M7 using XBTOOL and save a 256k image
open up both xbox's and locate the bios chips on the Modchip
remove both BIOS chips (not mixing them up)
place mates BIOS chip on his modchip but DONT seat it firmly, just use enough pressure for it to boot the box (my Mates box had Evolution X installed with bios flashing enabled)
ftp your patched BIOS to the BIOS folder in evox and reboot the box still using the little bit of pressure on the chip to make sure it boots
once booted remove your mates chip and firmly seat your BIOS chip and flash it with the patched EvoX M7 BIOS
once done power down your mates Xbox and remove your chip and put his back in and make sure his boots, lol
place your flashed chip into your box and boot, symptom 3 should have been fixed and the xbox should now boot
HOWEVER if you had a locked drive 
your pretty much screwed unless you saved your drive key too of which boot from a DVD with some sort of unlocking tool (I didnt need to do that as my drive was unlocked)Got to say, all worked in the end but with a load of scary moments, lol, now i just dont trust config magic, even if it was my fault in the first place, but as they say.. shit happens (need to find a way now of transferring the eeprom embedded on the BIOS BACK to the eeprom chip
Post by: Xboxler on October 29, 2004, 08:42:00 AM
I want to start configmagic, i press A an d then i get this message
"invalid xbox version specified"
What i have to do? i use the evox m8 1.6-bios
Post by: TRIaXOR on November 23, 2004, 05:08:00 PM
Used EEPROMagic to restore my backed up eeprom back to the eeprom itself (just make sure if/when you do it that you have a eeprom.bin file in the same dir) when it said restore successful i breathed a sigh of relief, rebooted the box and it ran, then relised that the bios still HAD an embedded eeprom in it
so I flashed EVO-X M8 to the bios and rebooted (holding breath ) then the M8 bios kicked in (Evox Logo on boot) i jumped up in joy woohoo, never will I ferk with Config Magic AGAIN.. (not unless I have a Spare Flashed Chip with an embedded eeprom in it, lol)
Post by: stick_man27 on November 30, 2004, 08:27:00 AM
So I fried my eeprom after playing NFSU2 (PAL)-
XBOX 1.5
X2.3b lite + (Running X2 4983 Bios)
Upgraded HDD (No Lock)
60mm Fan Mod.
Problem----->
Symptom #3 (Flashing Red)
After 2 days of reading and trial / error I got it back!!!
I think the only thing that saved my box here was way i flashed the X2 the first time
around. I left Bank 2 open with the cromwell on it. I tried reflashing several X2 Bios versions with the embeded eeprom with no sucess. It dawned on me this morning that
I had origionaly flashed Bank one with a 512k bios. So I created a new bios using the X2 4980.03 with XBtool using the "embed eeprom" then made it 512k with X2BM.
Reflashed bank two and viola!!! It worked.
Huge thanks go out to Skorchir.... I was almost ready to go buy a new XBOX today.
OH yeah.... I went back and DISABLED the EEPROM writeback feature in AVA. Wont be using that one again.....
Stick_man
Post by: phatboy on December 08, 2004, 11:57:00 AM
I have symtom #3. I accidently did the restore eeprom, in avalauch.
I don't have a backup of eeprom but I have obtained one now.
and I have also gotten the cromwell-patched.bin and addeeprom.exe
if I flash my bios using this, and then flash it with the latestet Xetuer bios and then install avalaunch again, will I lose all my games????
is there any ways I can save my games? back them up ?
--
Phatboy
Post by: ben1989 on January 04, 2005, 08:07:00 AM
