Post by: itzlilc on December 31, 2003, 07:38:00 AM
i have a x2.3 lite
Post by: Terrorbyte on December 31, 2003, 09:25:00 AM
| QUOTE |
| i get the sync=F message.....everything hooked up ok, except for my ground, could it be that? do i ground it into that little hole that says ground? because that means i would need to solder it. i have a x2.3 lite |
There should be a ground wire already on the programmer, unless you tore it off or something. Yes, you do need the ground hooked up, unless you want to fry your modchip.
You need to solder a wire from the X2 Lite programmer to the X2.3 Lite in order to get it to work; AND you need to temporarily short out your X2.3 chip by soldering two points together. The X2.3 modchip won't take power from the X2.0 Programmer (thanks to MS cutting the power to the LPC in v1.5 -- that's why the X2.3 Lite had to be redesigned to take power from the USB bus. The new X2.3B Lite takes all its power from the 5V connection). There is a Programmer v2.3 available now that works with the X2.3 Lite modchips, good luck finding it anywhere though.
As for other Sync problems, you have to set your LPT port in your PC's CMOS (BIOS setup) to Normal or ESS.
Post by: gro_ver on January 04, 2004, 11:29:00 AM
Ok i got a premodded xbox with the X2 lite chip installed. I flashed it with the wrong bios and corrupted it so I was told I needed to buy a programmer to fix it. I got it, hooked it up to my parallel port and am using the USB for power. I am using the 4979.06_256k.bin, and used x2bm to make a 1m bios.bin. When I plug in the chip to the programmer and give it power i get the 2 blue lights. Seems to be ok up to this point.
Problem:
When i type in "x2cable w bios.bin" into the command prompt to flash the bios it always gets to 6% and then just stops. ANY SUGGESTIONS!
Post by: seedy on January 10, 2004, 04:15:00 AM
.. 
Post by: seedy on January 10, 2004, 05:38:00 AM
Post by: Kedamono on January 31, 2004, 03:03:00 PM
Post by: wireless g on January 31, 2004, 03:56:00 PM
Post by: vtron70 on February 03, 2004, 09:35:00 AM
It took me a long time, but I finally figured it out. WIN LPC works to help x2cable see the driver. I also figured out that I was using x2 bios manager incorrectly. It's a very touchy prog, and even if you copy the bios wrong into the other banks, it flashes wrong. Apparently I had to put the 4981.06 bios in each bank instead of copying and pasting. I'm not saying that's the way you're supposed to do it, but it seemed to work for me. I then opened win lpc, closed it and made sure all of my usb ports were open except for the power to the programmer. I got out of all my programs that didn't have to do with the programmer. I reflashed cromwell first as a test to see if the xbox would go back to flashing orange(that meant my programmer was seeing my computer). Then I flashed 4981.06 for the millionth time and when I booted up my xbox, up came the xecuter screen. Hopefully this helps you with this problem.
Post by: boxman{Rage} on February 03, 2004, 04:06:00 PM
great tutorial followed it n got the chip reflashed nps just 1 question is it posiable to flash the chip whilst its in the xbox stuck on the side n hard wired or do i have to remove it the prog i got has extra wires with jumpers n also a pinhead part with pins n headder sorry but im new to this can do it nps whilst its out
Post by: osmonsat on February 03, 2004, 05:52:00 PM
Post by: osmonsat on February 03, 2004, 05:56:00 PM
| QUOTE (boxman{Rage} @ Feb 4 2004, 02:06 AM) |
| is it posiable to flash the chip whilst its in the xbox stuck on the side n hard wired or do i have to remove it the prog i got has extra wires with jumpers n also a pinhead part with pins n headder |
boxman - Download the FlashX program, install it on yor xbox and you should be able to re-flash your chip without removing it.
Post by: e-z on February 10, 2004, 05:14:00 AM
all these tutorials have been extremely helpful but my problem is somehow different from all the other before this:
i have 2.3B lite + external programmer, and when I connect them toghether (everything set up in the right way) the modchip just doesn't seem to work -> no blue light from the bright led.
Did anyone have problems like this? When the chip is inside the box, there's no such problems like this. I happened to flash it with wrong size bios and now I'm so full of this all...
thanks already.
Post by: vtron70 on February 10, 2004, 10:40:00 AM
Post by: e-z on February 10, 2004, 11:21:00 AM
| QUOTE (vtron70 @ Feb 10 2004, 10:33 PM) |
| e-z, you don't have the ground wire attached do you? |
hmm. the ground is connected to the motherboard of xbox - and i've tried unplugging it and putting the wire in it that i got with the programmer. maybe i'll give it another try... isn't it the one that's right next to the 12 pins?
this is SO frustrating.
Post by: vtron70 on February 10, 2004, 02:09:00 PM
Post by: j_Park on February 10, 2004, 03:41:00 PM
1. when i connect the ground wire from the chip to the programmer, the whole thing is shorted, causing the 2 red leds to go off, and causes my comp to restart if its connected usb. should i just connect the external switch to the chip instead? or does that cause it to not write/reflash correctly?
2. has anyone had an instance of x2cable completing the reflashing process, but the bios does not seem to work? because x2cable says it finishes writing every time, but the 'box still frags
3. i read on another post that xp has problems w/ either the programmer or x2cable, and that 98 is more compatible. has anyone else run into this problem, and if so, is it rather obvious that its having problems?
4. the blue external led no longer works, got burned out...is it used as just a signal for the chip or does it act as a diode, actually directing the flow of current, and might be causing the malfunction?
I'm not quite sure if this is a bios problem, or a reflashing problem, or a bad chip problem, etc., but any help/advice would be much appreciated.
Post by: e-z on February 10, 2004, 09:17:00 PM
| QUOTE (vtron70 @ Feb 11 2004, 02:02 AM) |
| Sorry, I should have elaborated. What I meant was, there was a wire that came with your programmer. And unfortuantely, the programmer doesn't come with an inventory list. But that wire, I found out the hard way, is for the older chips v2.2 and such. So you don't have to use that wire at all. The reason I asked is because I tried using that wire when I was having problems, and is shorted out my chip, causing my lights to not turn on. I was just trying to eliminate one of your prospective problems. I hope I didn't confuse you. |
thank you again, now i can forget that one wire. the problem is still standin' strong since the chip ain't getting power via the goddamn programmer. (but now i know that the wire simply isn't for my chip!)
respect.
Post by: duck1313 on February 27, 2004, 04:54:00 AM
Post by: Eyedea on February 27, 2004, 05:46:00 AM
I have yet to receive my chip but in reading the tutorials it looks like there is a "Flash" button.
Post by: NFCTinken on February 27, 2004, 11:46:00 AM
Post by: ni66e12 on February 28, 2004, 09:40:00 AM
Post by: Noyfb on March 10, 2004, 07:13:00 AM
i have executer 2.3b lite
i have the old style programmer
i am running xp
using x2cable
i tried a tut says set it to 95(compatability)
was getting sync errors (7)
tried windows 2000 compatability and it worked first time.
programmed and verified straight away.
best of luck everyone else
Post by: daghostmon on April 01, 2004, 04:34:00 PM
Post by: swese44 on April 30, 2004, 05:43:00 PM
Programmer I Have
I have an Xecuter 2.3B Lite. Each bank is 512KB, right? The tutorials I found say to make the bios 1 MB, which would take up the whole chip. How would this work with the bank switch? Would it only boot from one of the banks, and if so which one? Can I hook the chip up to the programmer the way it is, or do I have to solder or cut any wires on the programmer? Thanks a lot.
Post by: swese44 on April 30, 2004, 10:48:00 PM
Post by: dekor_one on May 01, 2004, 04:57:00 PM
this thing is a PIECE OF SHIT..
did i fry my chip? someone help please! i dished out a loit of $ for this shit
Post by: dekor_one on May 02, 2004, 04:46:00 AM
Post by: mykel on May 06, 2004, 09:32:00 AM
What does SYNC=1 mean? At first I had the ground from my 2.2+ plugged into the programmer. The lights would come on on the programmer, but not the chip. I disconnected the ground, and now both lights on the programer AND modchip light up. When I try to flash I get Error: SYNC=1. In X2BM, it says it can't detect the xecuter 2 chip 1x01010 or something like that.
What should I check?
Oh, I'll let it run all the way through and check my parallel port setting in the BIOS when I get home.
Post by: dindingwe on May 15, 2004, 03:51:00 AM
Post by: OpusDei on May 15, 2004, 04:47:00 AM
use x2bm v2.1 - if you get not detected or any error code its not reading your mod. the mod is either flash protected, cable not right or pc setups wrong. it is a very very rare occasion that the mod is faulty.
ive fitted and flashed hundreds of these mods - failure rate is not even 1 in a 100.
Post by: OpusDei on May 15, 2004, 04:48:00 AM
| QUOTE (dindingwe @ May 15 2004, 12:51 PM) |
| do you have any tutorials for the 2.3b lite chip? and my programmer does not come with a ground. is that really required? |
no the ground is not required - ive never used it
Post by: OpusDei on May 15, 2004, 04:48:00 AM
| QUOTE (dekor_one @ May 2 2004, 01:50 AM) |
| oh man.. i plugged in a ground wire into my 2.0 lite and trned my xbox on, smoke came from my chip and now when i turn it on i get 32 reboots and a shutdown... this thing is a PIECE OF SHIT.. did i fry my chip? someone help please! i dished out a loit of $ for this shit |
you did a bad install and made it smoke and call it a pece of shit ?
dont blame the tools bro........
Post by: BK4u on June 06, 2004, 02:40:00 PM
I have tried x2cable and I get an error sync=f.
Using X2pro I get an unable to start driver error.
And finally using xbox bios manager, it doesnt recognize the chip, something like 0xFFFFFF.
I have the switches on the chip set to enable, unprotected, and bank 1.
Can anyone give me a hand?
Post by: Jesusfreak on June 10, 2004, 01:33:00 PM
Thanks for the good tutorial, however; lite version doesn't need a ground, and need to use switch that comes with it instead of dip switch. it took a while to figure out.Post by: Llamma on June 10, 2004, 03:28:00 PM
| QUOTE (BK4u @ Jun 6 2004, 11:40 PM) |
| I have an x2 2.3 lite plus and I messed up flashing the bios with the cd's so now I have the trouble of trying to figure out this programmer. I have tried x2cable and I get an error sync=f. Using X2pro I get an unable to start driver error. And finally using xbox bios manager, it doesnt recognize the chip, something like 0xFFFFFF. I have the switches on the chip set to enable, unprotected, and bank 1. Can anyone give me a hand? |
ive sen a hundred times ppl saying use X2 Bio smanager v2.1 and not the old x2cable dos tool - did youread any of these posts in this thread ?
this threda is OLD stuff - new tutorials aremuch better and there are better apps
Post by: RoboChicken on June 12, 2004, 08:38:00 PM
Post by: BK4u on June 18, 2004, 10:24:00 AM
| QUOTE (Llamma @ Jun 11 2004, 12:21 AM) |
| ive sen a hundred times ppl saying use X2 Bio smanager v2.1 and not the old x2cable dos tool - did youread any of these posts in this thread ? this threda is OLD stuff - new tutorials aremuch better and there are better apps |
I did read a majority of the posts in this thread, and I tried X2 bios manager as I said before, I also just read in the readme that it works for the X2 lite, and X2 pro, but it doesnt say it works with the lite plus
Can you give me some links to some newer tutorials/apps? TIA
Post by: robstar on June 20, 2004, 07:22:00 PM
Post by: Dreamthief on June 22, 2004, 04:58:00 AM
wayyy too cool dude, loved the tutorial. worth framing i would say.i am running a v1.1 xbox, used the evox flash from the disk....oooops, didnt work out the way i wanted it too. so, back to the internet to order a flasher for it. got the flasher, ACTUALLY READ what you have posted( a first for me, trust me, as i seem to feel i can figure anything out on my own) found out that i was wrong. re-read the tutorial step by step, and flashed my xecuter 2.3b lite first time.
only problem was...the bios i flashed with was bad. read alot of other forums, and found out that if i get "error 16" coming up when i was unable to boot off my mod, it meant that the clock settings were bad. went to evox bios 4983.67
boom, fired up first time.
so check your bios versions, download a few more just to make sure. but dont give up hope yet...
there is always hope it seems.
Post by: elbrujo58 on July 21, 2004, 10:14:00 PM
Post by: aquiesce on July 22, 2004, 06:03:00 AM
Just thought id mention it incase you dont wanna put superglue on your new progger
Cheers
Great tut though
Post by: fuzzysack on July 30, 2004, 04:29:00 PM
Maybe it's windows XP..? I wish someone made a full win32 app of this program... That way you could rule out Legacy LPT port problems....I think XP don't like to support LPT ports in DOS.
Here is a thought make a bootable USB Pen drive with Cable 2 app and other junk... That way you will be in TRUE DOS.... This will only work if you bios (Motherboard) Supports booting from USB devices.
Post by: X-ecuter on August 02, 2004, 09:12:00 AM
| QUOTE (fuzzysack @ Jul 31 2004, 12:32 AM) |
| Maybe it's windows XP..? I wish someone made a full win32 app of this program... |
erm X2 Bios Manager v2.2
X2BM has been out for around a year now - its just that this tutorial is OLD
maybe ill do a new one ?
Post by: im_so_shibby on August 02, 2004, 12:10:00 PM
So what your saying is i can use X2BM 2.2 & X2cable in the same folder and i dont need the ground wire for a 2.3B Lite +. And instead of a ground wire use the external switch. THATS IT? 
Post by: X-ecuter on August 03, 2004, 01:11:00 PM
x2 bm is a standalone application - it programs both lite and pro as well as a bios creation and management tool
you should try downloading it and reading the readme file before asking questions
the ground wire hasnt been needed since X2.0
Post by: XdonX on August 05, 2004, 02:08:00 PM
- then i place the x2.3b lite plus modchip to the programmer,
the two blue led lights go on. then what's next ? connect the wire the they provide
with the programmer to the modchip then hook it up to where ? does it go on the programmer ? but when i do the lights all go out ?
- My computer i'm using is an Window Xp ? is that alright to use.
- when i hook up the wire that they provide. my computer freezes and i can't
do anything.
- when i go to MsDos i type the steps you say . cd x2 ---> c:x2 ---> x2cable r --->
unable to start driver ? what does that mean ?
PLS. let me know what i can do. i can't get my modchip flashed. Cause i flashed a bad on it. It really sucks cos i paid for the chip and i bought the programmer and i can't even get it to work. please help.
Post by: im_so_shibby on August 05, 2004, 09:33:00 PM
Post by: TKallstar on August 12, 2004, 12:36:00 PM
Post by: XplicitContent on August 12, 2004, 07:44:00 PM
BUT, instead of this tutorial, I used the one from modchipman.com in the "how to" section. It guides you using the X2 Lite Flasher, unlike this one. It really helps instead of using the X2cable method, the flasher does the x2cable for you easily. I'm sooo happy it didnt screw up! You guys should check out their guide, its good.
Post by: X-ecuter on August 23, 2004, 02:59:00 PM
there you go
Post by: seriouslysilly on February 11, 2005, 11:15:00 AM
Post by: Lerxst on June 08, 2003, 01:00:00 PM
(DISCLAIMER: I take no responsibility for anything that goes wrong with anything by using this tutorial! Period. Use this tutorial at your own risk) :)
Requirements:
1) X2lite Chip
2) X2lite programmer
3) PC with DB-25 printer port
4) DB-25 parallel cable male to female (shorter is better), or using my simple no cable mod. (See Fig.D)
5) Knowing how to create directories, unzip files and copy files basic stuff
6) A 1MB BIOS called bios.bin that you wish to flash the X2lite with. (I do not cover how to create the BIOS)
7) 9v 500mA DC power supply, or 9v alkaline battery, or open USB port on your PC
8) Software for the X2lite programmer (x2cable.zip). Get it here. or here
The first step is to make the connections of the various components as follows:
1) Connect the ground wire (Fig.A step 1) from the programmer to the X2lite chip. It has a little plastic connector and should fit into the slot on the X2lite chip. Do not force it, as it has a grooved connector that should fit only one way.
2) Connect the X2lite to the programmer (Fig.A step 2 and Fig.B ). There is a female socket on the X2lite, and a male header pin on the programmer. Flip the X2lite upside down and gently push the X2lite onto the header. Be careful not to yank the ground wire off of the programmer.
3) Remove the flash protection jumper (Fig.A step 3 and Fig.B )
4) Connect the parallel cable to the programmer (Fig.A step 4 ), or do the no cable mod (Fig.D ) and connect to the parallel port on your PC. (Note: if you are doing the no-cable mod and are using a 9v battery, you may want to insert it now because it will be more difficult to insert the battery when the programmer is attached to the PC)
Fig.A
(IMG:http://webpages.charter.net/aragon/images/figa.jpg) Picture of the parallel cable
Fig.B
(IMG:http://webpages.charter.net/aragon/images/figb.jpg) Picture of the 9v power adapter
5) Set the power switch according to the power source you are using. (Fig.C) If don't have a 9v power adapter, then just use a 9v battery by placing it in the battery cradle on the programmer. You can also use the supplied USB connection to plug into an open USB port on your PC. Just make sure to set the power switch according to your power source (Fig.C)
Fig.C
(IMG:http://webpages.charter.net/aragon/images/figc.jpg)
The no cable Mod
If you dont have a parallel cable, you can connect the programmer directly to your PCs parallel port by slightly modifying the connector plate that is screwed on to the X2lite programmer. The port on my computer had connector standoffs, and the programmer also has them, thus not allowing me to connect it directly to the PCs parallel port.
a) Use some needle nose pliers to remove (un-skrew) the two standoffs on the X2lite programmer connector plate. (Fig.D)
b ) Remove the connector plate. (Fig.D)
c) Apply two small dabs of superglue to two inside corners of the connector plate. (Fig.D) (Test the fitting BEFORE you apply the superglue so that you can get a feel for seating it correctly back in place)
d) Seat the connector plate back on the face and let set for a minute.
e) Done!
Fig.D
(IMG:http://webpages.charter.net/aragon/images/figd.jpg)
6) Connect the other end of the parallel cable to your PC. (Fig.E step 5)
Fig.E
(IMG:http://webpages.charter.net/aragon/images/fige.jpg)
7) Connect the power to the programmer. (Fig.F step 7)
Fig.F
(IMG:http://webpages.charter.net/aragon/images/figf.jpg)
Connections finished.
The next steps are to set up the x2cable software and program your X2lite.
1) Create a directory on your C:\ drive called x2
2) Unzip/extract the x2cable.zip to the folder you created in the previous step
3) Copy your bios.bin file into the x2 folder that also contains the extracted files from the previous step
4) Now open a DOS command prompt by selecting: Start>Programs>Accessories>Command Prompt (See Fig.G)
Fig.G
(IMG:http://webpages.charter.net/aragon/images/figg.jpg)
5) In the command prompt you just opened, type:
cd C:\x2 (See Fig.H)
Fig.H
(IMG:http://webpages.charter.net/aragon/images/figh.jpg)
Then type: dir and it will list all the files. (This should match Fig.H)
6) Now test the programmer by reading the BIOS first before writing (Fig.J). (if your X2lite came pre-flashed with Cromwell 1.8) Type the following:
x2cable r crom19.bin
(This will take approx. a minute and a half to complete)
Fig.J
(IMG:http://webpages.charter.net/aragon/images/figj.jpg)
If you are getting SYNC=variable here, then there is a power or connection problem, or the parallel cable is too long.
7) Now it is time to flash the new BIOS onto the X2lite (Fig.I). Type the following:
x2cable w bios.bin
(It will then erase and begin writing the BIOS to your X2lite. This process will take approx. eleven minutes, and will then verify the write for another minute and a half.)
Fig.I
(IMG:http://webpages.charter.net/aragon/images/figi.jpg)
8) Done!
~Lerxst
EDIT: I have more pictures, but I'm at the limit.
EDIT: Picture sizes smaller, typos
This post has been edited by Lerxst: Jun 9 2003, 04:55 PM
Post by: spIdeZ on June 08, 2003, 01:14:00 PM
Have you submitted it to be a tutorial?
Post by: Lerxst on June 08, 2003, 04:59:00 PM
| QUOTE (spIdeZ @ Jun 8 2003, 04:07 PM) |
| Nice, very detailed Have you submitted it to be a tutorial? |
Thanks. I will submit it, but some of the pictures are over the 400 pixel limit, so they my not accept it even though those pics are smaller than the rest. If I resize the command prompt pic's, they become unreadable. (at least for my old eyes).
~Lerxst
Post by: Lerxst on June 09, 2003, 09:10:00 AM
Someone may need this.
~Lerxst
Post by: loquillo on June 09, 2003, 05:59:00 PM
Hey man your the beeesstttt!!!!! this tutorial work best than any other that I read or see!!!!! oh and another thing I do the tutorial with windows 98 SE and works perfect ok!!!! and another thing than youuuuuuuuuuuu very muchhhhhhh!!!!! This programer rocks!!!!!!Post by: loquillo on June 09, 2003, 06:01:00 PM
this tut it works!!!!!!!!!!
Post by: Lerxst on June 10, 2003, 06:13:00 PM
| QUOTE (loquillo @ Jun 9 2003, 08:52 PM) |
| Hey man your the beeesstttt!!!!! this tutorial work best than any other that I read or see!!!!! oh and another thing I do the tutorial with windows 98 SE and works perfect ok!!!! and another thing than youuuuuuuuuuuu very muchhhhhhh!!!!! This programer rocks!!!!!! |
Hey thanks! - I'm glad this has helped, and I appreciate the kudos.
If there is anyone else who would like to provide some feedback on this, it would be much welcomed. I want to submit this tutorial, but I would like to get more eyes to look at it first.
Thanks,
~Lerxst
Post by: Foolio on June 10, 2003, 11:33:00 PM
Post by: Dunny on June 12, 2003, 04:00:00 AM
If you keep getting Sync 7 Errors when flashing, use X2PRO instead ... I tried X2cable on 3 Machines today and it wouldnt work on any! Tried X2PRO, flashed a 256k Bios to 1 and it worked .... at last!
Post by: Lerxst on June 12, 2003, 08:29:00 AM
| QUOTE (Dunny @ Jun 12 2003, 07:00 AM) |
| You may want to add this to your instructions. If you keep getting Sync 7 Errors when flashing, use X2PRO instead ... I tried X2cable on 3 Machines today and it wouldnt work on any! Tried X2PRO, flashed a 256k Bios to 1 and it worked .... at last! |
Thanks for this! Iwill work with X2PRO and see what I get. I was not able to reproduce SYNC=7 with the x2cable method.
I will update later tonight.
~Lerxst
Post by: Morglum on June 14, 2003, 06:13:00 AM
Post by: compcwby on June 17, 2003, 03:45:00 PM
I am able to run x2cable i with a few of these errors, but at this point, I don't have a clue anymore.
Post by: feflicker on June 22, 2003, 04:46:00 PM
Will the external programmer work on the X2Pro version?
I know it probably wont work with an X2Pro (since it requires the external switch module), but what about an X2.1Pro or the new X2.2Pro that is coming out (they don't require the external switch module to operate)?
A question for "Uber" maybe?
Just curious, I just ordered one of these.... I don't like the external programmer that comes with the X2Pro, so I was hoping I could use this instead... If not, will settle with just using this on my X2Lites. I can't take anymore of that Ozxflash CD and it's "wait 30 seconds" business
---------------------------------------------------------------------------------------------------------------------------
On the parallel port issues, my *guess* is that the pre-compiled x2cable.exe is hard coded to look at 378h parallel port address (the most common address). That is why it only works on 1 parallel port
If you have problems, make sure your parallel port is set to ECP in bios, it might help...
Post by: Lerxst on June 22, 2003, 11:09:00 PM
| QUOTE |
| Great tutorial! A few questions: |
Thanks!
| QUOTE |
| Will the external programmer work on the X2Pro version? |
Very good question. I was going to work on testing this with the pro I had, but someone bought it. I plan on getting some more in stock as I seem to be one of the few who does mods around where I live.
| QUOTE |
| I know it probably wont work with an X2Pro (since it requires the external switch module), but what about an X2.1Pro or the new X2.2Pro that is coming out (they don't require the external switch module to operate)? |
I do believe that it is possible for it to work. I can't say with confidence, but the pro is a BIOS chip that can take a 1MB BIOS. So that leads me to believe that it is very possible to flash the pro with this programmer. I've got one on order.
| QUOTE |
| A question for "Uber" maybe? |
If he has any input to add - it would be appreciated. I want to make this tutorial as complete as possible.
| QUOTE |
| Just curious, I just ordered one of these.... I don't like the external programmer that comes with the X2Pro, so I was hoping I could use this instead... If not, will settle with just using this on my X2Lites. I can't take anymore of that Ozxflash CD and it's "wait 30 seconds" business |
I hear ya! I can't stand flashing with the CDRW's, although it was the only option I had when I first started. The programmer has worked great for me so far.
I plan on adding a trouble shooting addendum to this tut. as many have PM'd me with problems/solutions that I will detail soon. I am not ready to submit this yet, as there are still outstanding issuses that need to be resolved.
| QUOTE |
| On the parallel port issues, my *guess* is that the pre-compiled x2cable.exe is hard coded to look at 378h parallel port address (the most common address). That is why it only works on 1 parallel port If you have problems, make sure your parallel port is set to ECP in bios, it might help... |
Yes, that is the default port, and I have found that you can also change the port that x2cable looks at if you type in "x2cable" in the command prompt - it shows you the options for redirecting the port that it will use.
~Lerxst
Post by: musical_mercenary_420 on June 23, 2003, 07:42:00 PM
Post by: DaveHShapiro on June 26, 2003, 12:27:00 PM
HELP!!!
however I did take your comand prompt images and compressed them so this can be a tutorial.
need me to compress all the images?
I can also make them smaller i think.
http://deep-shadows.net/xbox/figh.jpg
http://deep-shadows.net/xbox/figi.jpg
http://deep-shadows.net/xbox/figj.jpg
Post by: TheUnluckyCharm on June 26, 2003, 07:27:00 PM
Post by: Lerxst on June 27, 2003, 03:13:00 PM
| QUOTE (musical_mercenary_420 @ Jun 23 2003, 10:35 PM) |
| ok of my understanding you can use this for the x2lite 1.2's? |
Yes works fine.
~Lerxst
Post by: feflicker on June 27, 2003, 05:48:00 PM
I am using the "no-cable" mod, with the USB giving power. The switch is set correctly, the chip is ready to flash, grounded, etc.
I got x2pro.exe, from x-bins, and it worked first try! (x2pro w0 bios.bin)
I am running XP Pro...
EDIT:
Great, got the "Error at location 00000h! Read [10] Actual [9]" error... Hmm...
EDIT2:
Well, this didn't work (using x2pro.exe instead of x2cable.exe)! I erased the chip a few times, and tried to write to it, each time with a 1mb bios file. Kept getting the error above... When I popped it in, still had cromwell on it! The *erase* didn't even work.
Apparently it *looks* like it is working, but is not doing anything
Also, had my BIOS set to Bi-Directional, EPP, and ECP. No difference... Even tried setting the exe to be emulated as win95/win98... That helped it to run, but still got the above errors!
I am at a loss... Next time I will try it on my laptop...
Post by: musical_mercenary_420 on June 27, 2003, 08:32:00 PM
Post by: feflicker on June 28, 2003, 07:39:00 PM
Also, another guy used a rubber band to hold the chip on the programmer tight. That seemed to help his issue as well.
I still can't get past the "Sync 7" errors using xbcable, or the "00000h" error using x2pro.
I have tried all bios combinations on my parport, different emulation for the exe, no cable-mod, etc...
I still can't get xbcable to recognize the programmer!
(Still need to try my laptop... <fingers crossed>
I also uninstalled my printer driver and zip drive driver. Then I tried installing the GiveIO driver (for the matrix programmer) just to see if it would help. Nope!
Post by: underthebridge on June 29, 2003, 08:42:00 AM
Post by: musical_mercenary_420 on June 30, 2003, 09:53:00 PM
Post by: bigga on July 01, 2003, 05:56:00 AM
Post by: trbnbill on July 03, 2003, 05:18:00 PM
Good Job.
I can't understand why they can't ship simple usage instructions with the programmer as it is supposed to be totally legal to use. I looked forever for instructions and stumbled on your post and am very greatful!!!!!!!!
trbnbill.................
Post by: Kev052683 on July 04, 2003, 05:37:00 PM
Post by: Ian on July 04, 2003, 06:16:00 PM
Post by: Kev052683 on July 04, 2003, 07:09:00 PM
Post by: Ian on July 04, 2003, 09:15:00 PM
Post by: 4me2 on July 05, 2003, 02:54:00 AM
Many thanx.
Post by: freaky on July 05, 2003, 03:05:00 AM
so CHEERS m8 and have some more kudos
KUDOS
Post by: thomes08 on July 05, 2003, 12:23:00 PM
thomes08
Post by: thomes08 on July 05, 2003, 12:30:00 PM
thanks
thomes08
Post by: feflicker on July 05, 2003, 12:34:00 PM
Post by: thomes08 on July 05, 2003, 01:14:00 PM
thanks
thomes08
i dont need a detailed tut with pictures just the commands that should work will be fine
Post by: thomes08 on July 05, 2003, 02:16:00 PM
Post by: thomes08 on July 06, 2003, 10:54:00 AM
Post by: thomes08 on July 06, 2003, 04:02:00 PM
Post by: FIREitUP on July 06, 2003, 04:04:00 PM
| QUOTE |
| PIN!!!! |
Post by: thomes08 on July 06, 2003, 04:26:00 PM
"On the parallel port issues, my *guess* is that the pre-compiled x2cable.exe is hard coded to look at 378h parallel port address (the most common address). That is why it only works on 1 parallel port If you have problems, make sure your parallel port is set to ECP in bios, it might help..."
i looked in my device manager and the looked in the properties of my printer port, then hit the recourses tab and saw that my I/O range is from 0378 - 037F. I dont think that that is what is should be at but i'm not sure. Could anyone tell me how to change the I/O range to one that will read 378h or tell me how to change xbcable so it will be in the range my printer port is at..... OR tell me how to use x2pro flashing program.... any help would be great. thanks
thomes08
Post by: arnaro on July 07, 2003, 10:19:00 AM
when I just type x2cable it says LPT Port default to 378h so
I guess its reading the port.
Im using XP Pro....
Please help Ive got two chips that need flashing (have a corrupted bios)
Post by: feflicker on July 07, 2003, 10:24:00 AM
Change it to ECC or ECP.
Post by: noobiex on July 07, 2003, 12:34:00 PM
Your tutorial was very helpful for me. I used it to flash my x2pro. Worked great. At first i was getting the sync errors to, so on the external programmer I removed the black pin spacer where the chip plugs up to and presto !!! Worked flawlessly !!Thanks For the Help !!!!
Post by: Ubergeek on July 07, 2003, 12:39:00 PM
Post by: arnaro on July 07, 2003, 01:13:00 PM
I noticed that in ECP I can selected USE DMA 1 or 3
And in ECC I can select ECC 1.7 or 1.9
Also when I have ECC/ECP on I can selecte all of the above.
Now thats about 8 possibilities in all... !
Any pointers... ?
----------------------------------------------------------------
change port settings to ecc or ecp
---------------
I just get an error as soon as I try to run x2cable with params.
when I just type x2cable it says LPT Port default to 378h so
I guess its reading the port.
Im using XP Pro....
Please help Ive got two chips that need flashing (have a corrupted bios)
Post by: feflicker on July 07, 2003, 01:50:00 PM
In addition, some mobo's are just plain incompatible with the programmer software
If you fail on one pc, try another... It might work first try
Post by: DJLink on July 07, 2003, 06:45:00 PM
when I change the properties back to xp I get the unable to start driver again.
How do you change the LPT port in the Bios? feflicker sugested that but I don't know how to do it.
I am running windows xp pro and have a x2.1 light chip.
I am using the no cable method. both power lights are lit.
Please Please help!
Post by: Lerxst on July 07, 2003, 07:05:00 PM
| QUOTE (DJLink @ Jul 7 2003, 09:38 PM) |
| I am having the unable to start driver problem as well. Just like thomos08 did. I also tried changing the propertios on the x2cable exe to win 95 like suggested then I get the error 7 when I change the properties back to xp I get the unable to start driver again. How do you change the LPT port in the Bios? feflicker sugested that but I don't know how to do it. I am running windows xp pro and have a x2.1 light chip. I am using the no cable method. both power lights are lit. Please Please help! |
Okay,
Sorry I have not been able to update this tutorial, but things at work are keeping me from the forum - waaa
Anyway, if you get the "Unable to start driver!" error, you should do the following:
Download Win_LPC unzip it, then execute it. It won't run correctly, but it will free up the resource to allow the driver to start. Close out win_lpc.
Then just go back to a DOS prompt and start over. It should work after this. I did not have to make any changes in the BIOS for any of this to work.
~Lerxst
EDIT: Also, I've been getting a questions on if the USB cable can be used for programming. The answer is NO. It is only used as a alternative power source.
Post by: thomes08 on July 07, 2003, 08:25:00 PM
good luck to everyone you'll get it if you keep trying.
thomes08
Post by: DJLink on July 07, 2003, 09:32:00 PM
the first time I ran win lpc I got an error saying device not found please check your setting.....bla bla
I then tried the dos commands again x2cable and get error 7.
Next I restarted my machine and ran win lpc again, and this time it actually ran and gave me 3 choices of what to do for installing a bios. one choice was to install a 1 mb bios. I pressed it and it promted me to find a .bin file. So i went to my bios.bin opened it and then win lpc got some errors and closed.
I then tried to use x2cable again and I get error 7 every time. I use to get unable to start driver, unless I changed the properties to win95.....Now I get error 7 everytime even when I restart my computer delete everything and start all over again
I've also tried this on 3 different computers at my parents house before I got your message about win lpc. And I had all the same results on each: unable to recognize driver. (I uninstalled all printing/scaning/zip drivers on every pc I've tried)
Now after win lpc my home computer just gives error 7 no matter what.
If anyone knows anyway to fix this please please help!
And I want to thank Lerxst again for spending time on this tutorial, and helping so many people. Any further help with my problem will be greatly appreciated.
Thanks,
DJLink
Post by: Fragzen on July 08, 2003, 06:46:00 AM
1. X2Cable must be run in Win95 / Win98 compatible mode.
2. X2Pro might work where X2Cable doesnt.
Greeds
Post by: Fragzen on July 08, 2003, 06:51:00 AM
After going through some rough times Ive finally been able to run X2Cable and also getting rid of the Error Sync=7....
But now I always get an error when the writing finishes ... Error 00000h I think it is... What steps should I take from here ?
Make the bin file again... The file works as I put it on a CDrw and used OZxflash to flash it on several chips. Now Ive only got two chips left that I need to but the bios on but I always get this error (BTW they were the first two that I tried using OZxflash, but the bios was incorrectly made then)
So my question is "If Im getting this error 00000h (00000f dont remember which it was as Im at work now) what can I do ?"
Greeds.
Post by: DJLink on July 08, 2003, 09:23:00 AM
I have also tried installing win lpc as suggested, and it runss the first time you try it on a new computer. It gives me 3 choices of what to do for installing a bios. one choice was to install a 1 mb bios. I pressed it and it promted me to find a .bin file. So i went to my bios.bin opened it and then win lpc got some errors and closed. I then tried to use x2cable again and I get error 7 every time.
When I re-try installing win lpc on a the same computer I get device not found, instead of it running.
I am now on my 5th computer. I've tried everything. WTF(who made this programer, it is crap) And who said that x2 light are better for newbee's if you have a bad flash thier are freaking impossible to reporgram, while the pro chips are very simple to reprogram with new bios.
Maybee I have a bad chip. I don't know(I do know that the programer is a peice of shit and should not be this hard to use), I hope consol corner will exchange this chip and programer, which I've spent over $60 the the chip plus shipping and programmer and 14+ hours trying to flash it. on for an x2.1 pro or x2.2 pro. All my friends that have the pro chips have no problem flashing them.
Does anyone know if consol corner will exchange or who to contact from team xecutor for an exchange.
Post by: feflicker on July 08, 2003, 02:08:00 PM
Like I said earlier, it is all luck if your OS/PC Motherboard "talk" in the way this software requires
Luckily my laptop works 1/10 tries
Post by: DJLink on July 08, 2003, 02:25:00 PM
Maybee got unlucky and got a bad chip or maybee its the programer(which is the worst product ever made).
Anyways it does not work and I've tried everything!
thank god I bought my chip and programmer from consol Corner they are the best. They e-mailed me back immediatly with details for exhcanging the faulty chip and programmer for a x2.x pro
ADVICE FOR ALL NEWBEE'S LIKE ME, WHAT-EVER YOU DO NOT BUY A X2LITE, GET THE PRO.
I CANNOT BELIEVE ALL THE THE CRAP ON WEBSITES AND FORUMS RECOMENDING THAT NEW-BEES GET THE LITE. IF IT DOES NOT FLASH RIGHT YOU ARE SOL.
IF OZFLASH DOES NOT FLASH YOUR X2 LIGHT CHIP CORRECTLY, YOU ARE FUCKED B/C IT ERASES LINUX AND THEN YOU HAVE TO BUY THE PROGRAMER(WHICH IS A FUCKING NIGHTMARE)
PROGRAMING THE PRO IS SO MUCH EASIER PLUS IT WORKS AND THIERS TONS OF SUPPORT TO PROGRAM IT, ESPECIALLY FOR WHEN NEW BIOS COME OUT.
SO BASICALLY, IF YOU ARE GOING TO BUY A CHIP AND YOUR A NEWBEE, i STRONLY ADVISE YOU TO GET THE PRO.
Post by: Kev052683 on July 08, 2003, 03:55:00 PM
Post by: Lerxst on July 08, 2003, 05:21:00 PM
| QUOTE (Fragzen @ Jul 8 2003, 09:39 AM) |
| Couple of things that should be added to this tutorial. 1. X2Cable must be run in Win95 / Win98 compatible mode. 2. X2Pro might work where X2Cable doesnt. Greeds |
This is not correct in my expierence. I have never had to run in compatability mode for this to work, and when I have, it has errored with sync 7's. X2pro has not worked either. It may look like it is, but there is actually no flashing of the chip.
If you are getting the sync 7 errors - the programmer/chip is not communicating - and is not being seen.
~Lerxst
EDIT: Also, I have installed/flashed many x2lites some with tester123 OzxChip Method, and most with the programmer. The only time that I have ever had problems with the programmer is when I am actually trying to make it not work. Some things that I have tried are:
1) Disconnecting the power before trying to flash (sync 7)
2) Disconnecting the parallel cable (sync 7)
3) Diconnecting the ground wire from the programmer (you guessed it)
etc. etc.
Again, if you are getiing sync 7 errors and you are running in 95/98 compatability mode, make sure you change it back. Same with your BIOS settings. If you have changed it to run in "normal" mode, change it back to ECP or whatever it was.
I have not gotten the programmer to work under WinME, and I really didn't work at trying to figure out why but it also erorred with sync 7's.
Post by: Kev052683 on July 08, 2003, 05:34:00 PM
Post by: Fragzen on July 09, 2003, 10:55:00 AM
Further I have not been able to run x2cable without running it in Win 95 or Win 98/Me compatibility mode. I always get a message Windows is unable to run this program etc.
I dont agree with your comments on only having problems while not trying to make it work. Well if you are trying to not make it work, it wouldnt be a problem when it doesnt now would it
I must say that I tought this would be a walk in the park compared to the OZxflash method but boy was I wrong.
Now Im left with two chips that I flashed incorrectly with that method that wont boot up in Cromwell so I have to flash them with the programmer. I figured it was cheaper to buy a programmer then to scrap them. Again boy was I wrong. Now im UKP65 down instead of UKP50...
Post by: Lerxst on July 09, 2003, 08:26:00 PM
| QUOTE |
| I dont agree with your comments on only having problems while not trying to make it work. Well if you are trying to not make it work, it wouldnt be a problem when it doesnt now would it |
I'm sorry that you have not been able to get the programmer to work for you. Please don't misunderstand what I said about trying to make the programmer not work. The reason why I did this in the first place was to get every error I could so that I could help you - and others that might have the same problem.
Once again the only time that I have had problems is when I have tried to create an error condition that someone else has posted about. So, I think that there is a troubleshooting mentality that goes along with what I have posted, and hopefully others will see and adopt this for themselves to be able to figure out what it is that they could possibly be doing incorrectly, or correct a configuration issue that has absolutly nothing to do with the programmer itself.
Moreover it is Microshaft's wonderful OS that has no clue, and this is why I spend so much time trying different things so that I can repeat the same condition that is probably due to a single source.
There is no walk in the park with M$. It is only a matter of how much "vasoline" you have in hand - pun/no pun
I think your programmer actually works. It's something else that is causing the problem
I would like to help you more to figure out exactly what error conditions you are getting. Maybe you could PM me with a detail of OS - hardware - configuration etc. If we have success, it will be more the advantage of those who read this thread when we are done.
I'm sick, I love puzzles - maybe that's why I play video games (vidiot)
~Lerxst
Post by: mmphoneman on July 10, 2003, 02:07:00 PM
MM
Post by: mmphoneman on July 10, 2003, 03:15:00 PM
I feel so close to getting this resolved. Thanks for the help in advance.
MM
Post by: Lerxst on July 10, 2003, 03:47:00 PM
| QUOTE (mmphoneman @ Jul 10 2003, 06:08 PM) |
| Well, I guess I should have read all of these posts. I finally got it to not say "unable to start driver". Now I get "ERROR opening bios.bin" I feel so close to getting this resolved. Thanks for the help in advance. MM |
If your x2lite came pre-flashed with cromwell, you might want to read it into a bin file, and then write it back to the chip. The reason why I say this is that it will tell you if the original bios.bin file was made correctly. (The one that errored)
If it flashes back to the chip succesfully, then you know that you may need to go back and create your bios.bin file again.
~Lerxst
Post by: mmphoneman on July 11, 2003, 08:48:00 AM
Post by: Lerxst on July 11, 2003, 09:04:00 AM
| QUOTE (mmphoneman @ Jul 11 2003, 11:41 AM) |
| I finally got it to flash the chip. In my case it happened to be a misaligned programmer when I connected it to the LPT.(direct connect) When I reinstalled it back in my Xbox it still says $icrosoft under the X. Shouldn't it say xecuter2? That is the bios I'm using. |
If it boots to the M$ bios with the chip enabled, it is most likely that D0 is not getting a good connection. Re-solder your D0 point and double-triple check it.
~Lerxst
Post by: ukplum on July 14, 2003, 02:11:00 PM
Post by: ukplum on July 15, 2003, 09:49:00 AM
Got it home and yeh u guessed it..sync7 error.
So in all i wasted my money and time.. shit
Im running xp PRO any suggestions?
Post by: freaky on July 21, 2003, 02:21:00 PM
so nice one m8, cool tute
cheers
Post by: fudgeit2k on July 23, 2003, 08:15:00 PM
I'm trying to write a 1 M bios with x2cable... it worked with my old x2.1 lite modchip, so I'm wondering if anyone know what the deal is. Could it be a bad modchip ?
Post by: PsychoZX on July 23, 2003, 10:22:00 PM
Post by: Falcon1433 on July 29, 2003, 05:13:00 PM
Post by: moultonrock on August 03, 2003, 12:18:00 AM
But I'm getting an error. It shows:
Writing...Done. Time taken=504s.
Error at location 00060h!
The writing process finished 100% then this error came so I am really confussed about what happened. I've tried it 3 times and the same thing happens.
I have a x2.1lite with cromwell on it and I used x2cable on win2k.
Post by: bho76 on August 06, 2003, 10:34:00 PM
ok great article but i cant even get a sync error. all i get is- unable to start driver!
what is goin on with this?? I followed directions and made sure my port was set correct. Where do i go from here?
thanks
Post by: Lerxst on August 07, 2003, 03:56:00 AM
| QUOTE (Lerxst @ Jul 7 2003, 10:05 PM) | ||
Okay, Sorry I have not been able to update this tutorial, but things at work are keeping me from the forum - waaa Anyway, if you get the "Unable to start driver!" error, you should do the following: Download Win_LPC unzip it, then execute it. It won't run correctly, but it will free up the resource to allow the driver to start. Close out win_lpc. Then just go back to a DOS prompt and start over. It should work after this. I did not have to make any changes in the BIOS for any of this to work. ~Lerxst EDIT: Also, I've been getting a questions on if the USB cable can be used for programming. The answer is NO. It is only used as a alternative power source. |
I'll try to update this tut. with trouble shooting steps this weekend, but until then - I'll quote myself.
~Lerxst
Post by: bho76 on August 07, 2003, 11:20:00 AM
Post by: xboomx on August 08, 2003, 10:07:00 PM
Post by: static_child on August 09, 2003, 10:54:00 AM
error at location 00000h! read[10] actual[9]
means?
i get sync 7 errors using x2cable
and this is what i get when i use x2pro.
i'm trying to flash my x2.2lite+ chip and nothing is working.
i'm getting really frustrated.
please help.
Post by: Mr.187 on August 12, 2003, 01:30:00 AM
Post by: petah on August 12, 2003, 04:30:00 PM
| QUOTE (static_child @ Aug 9 2003, 07:47 PM) |
| do any of you guys know what the x2pro error message: error at location 00000h! read[10] actual[9] means? i get sync 7 errors using x2cable and this is what i get when i use x2pro. i'm trying to flash my x2.2lite+ chip and nothing is working. i'm getting really frustrated. please help. |
I get a very similar error (with x2pro)..
writing...done time taken = 294s.
error at location 00000h! Read [00] actual [ff}
1mb mode
ive tried all different sizes, different bios, x2cable (get synch letters of all sorts) and everything else i know of.
. it is infuriating. keep thinking its done, but really im just getting irritated. pooh.
please offer words of wisdom or encouragment
UPDATE:::
worked. finally here's how. bios setting required bothways or some shit like that . not ecp or epp or the other crap. atleast fro my comp (hp 2400 amd athlon w/ one printer port.) i used x2cable, pro didnt work for me at all. said it did but gave me a 0000h error everytime.
finally i got t to work by putting my bios in the x2 directory. opening dos prompt, getting everything set to go, (i.e x2cable r bios.bin (i used 4976x2 if you care)). then before i entered it i closed all programs and processes i could (running xp incidentially and didnt use any 95 compatability (tho i tried earlier this evening)) then ran the win LPC program lerxst mentioned a couple of times. (see page 4 of these posts). after i ran it i killed it clicked my dos (emultaion
window and pressed return then didnt touch it tillit was done (about 15 mins). the first time i got one error so i tried again and it worked.
incidetially think carefully about what bios you decide to load. i was using x2 4976 before i started this whole fiasco by trying to update to 4977. i actually did this mthod w/ 4977 and thought it worked but the box wouldnt boot . i happened to have a copy of my evo conf i had ftp'd to my comp tho and looked through and didnt see 4977 mentioned in any of the roms listed. i dont even know if it matters but something to consider.......
so good luck people. keep at it. and Lerxst - thanks man. saved my ass.
Post by: extcyrolls on August 13, 2003, 05:22:00 PM
| QUOTE (static_child @ Aug 9 2003, 07:47 PM) |
| do any of you guys know what the x2pro error message: error at location 00000h! read[10] actual[9] means? i get sync 7 errors using x2cable and this is what i get when i use x2pro. i'm trying to flash my x2.2lite+ chip and nothing is working. i'm getting really frustrated. please help. |
this is the exact same thing that's happening w/ my x2.1 lite
------------ edit ----------------
I got my chip flashed w/ the programmer on a diffrent pc
The pc I was using has a ASUS A7M266-D mobo, 1G pc2100ddr,2 Athlon XP 2000+ running Windows XP Pro. I tried x2cable and in winxp w/o compatibility I kept getting a program error and windows would, force close. In 98/ME compatibility I kept getting sync error=7. I tried x2pro and it would seem fine till verify and then I would get error at location 00000h! read[10] actual[9]. So after perusing this thread (which has alot of helpful info) I seen alot of posts saying try a diffrent pc. So I pulled my old Packard Bell Multimedia 5606 233MHZ intel celeron and 64MB pc100 running Windows XP pro out of the closet (literaly) and hooked it up. I started with the x2cable ( not in compatibilty mode ) method and @ first recieved sync error=f, I tried the win lpc method described in this thread, success no error, put my bios.bin file together used evox d.6 eject fix in bank 1 &2 and x2 4977 in 3 &4. and wrote with success. Thought I'd describe everything in case it helps someone out. In any case this was a good tutorial but the programmer is very picky about which setup it want's to work with.
Post by: Copter64 on August 15, 2003, 07:06:00 AM
error:sync=d
Post by: overc00k on August 20, 2003, 08:23:00 PM
| QUOTE (static_child @ Aug 9 2003, 07:47 PM) |
| do any of you guys know what the x2pro error message: error at location 00000h! read[10] actual[9] means? i get sync 7 errors using x2cable and this is what i get when i use x2pro. i'm trying to flash my x2.2lite+ chip and nothing is working. i'm getting really frustrated. please help. |
almost the same but i get
error at location 00000h! Read[ff] Actual [09]
Post by: tommyd on August 21, 2003, 11:46:00 AM
With X2pro.exe it finishes up to 100% then I get this error:
error at location 00000h! read[10] actual[10]
When I use x2cable.exe I get the following scrolling down my screen:
Error: Sync=7
Any Ideas anyone? I'm starting to lose hope.
Thanks in Advanced
Post by: Pachoohiromi on August 21, 2003, 08:00:00 PM
Post by: Gokut on August 22, 2003, 08:51:00 PM
I got my programmer last week and I have been having alot of problems. Majority of the problems are the same as what you guys are having. I used WInLPC and it gives me F errors.. What could this mean?
One guy told me that it could be a bad connection via USB which is what I am using. I can get a battery tommrow but I really dun feel like going out of the way for this.
Let me know thanks!
Post by: NFCTinken on August 22, 2003, 09:41:00 PM
I had an issue (like many other today) when I tried to flash my X2 Lite 2.0 to the 4978 BIOS and I relaize that this flash is causing my Xbox to frag. I ordered the programmer today and just had a question on which BIOS I should load to get the unit back up in running. Do I need to go back to a Cromwell BIOS or can I go back to the 4977? And before I go to either of those BIOSs' do I need to erase the existing bad flash or when I write the new one will it get rid of the bad one? I suppose that was 2 questions, but any help would be appreicated. Thanks again for the nice tut. I will keep you informed on how things go.
Post by: LateraLex on August 24, 2003, 01:18:00 PM
i got sync error f, but reseated the programmer, and everything seemed to be working fine. i can read the bios, but when i go to write i see that it erases the bios, but then stops at 2% when writing. however the cpu is still running x2cable even when it is frozen. how bizarre... any ideas?
Post by: M.A.D Agent on August 25, 2003, 07:53:00 PM
Post by: BrianM on August 25, 2003, 08:42:00 PM
First hurdle, I have the X2.2L+ (someone else had luck using this with the programmer and not having the ground hooked up, so I'm not to worried about this).
I have the programmer running on USB power, no cable mod (doesn't seem to work right with a new 9v), occasionally get Sync 1/7 errors but more often than not it looks like it's working per the tut.
I have the switches set to "enabled", "unprotected", and "Bank 1"
I'm trying to push the X2 4977 1024kb file (so I should have the right size down ~ DL from #Xbins)
After flashing, if I 'x2cable r checkfile.bin' ~ I do get a file of the exact same size which would lead me to believe I have a proper flash ~ still FRAGS
After each and every "successfull" flash I test out the chip and always get a FRAG with the chip enabled, normal M$ when disabled.
Things I'd like to know - is anyone else having this exact same issue? Is there a better Bios I should be using/try? Any other suggestions (asside from buy a PRO ~ I wanted this to be a 1 time deal dangit.. :/ )
-----------edit---------------
Well, this is interesting - if I do an 'x2cable e" then 'x2cable r test.bin' I always come up with a 1mb file. I tried erasing with x2pro and then reading with x2cable - shows a 1mb file (1024kb) ~ so apparently it's NOT erasing. Lovely...
--------- 2nd edit------------------
The stars aligned after I DLed the X2_4977 bios from a UK site instead of Xbins ~ has anyone flashed properly with the Xbins bios ~ maybe it's corrupt. In anycase, onto Evox...
Thanks in advance.....
Post by: Fredb on August 26, 2003, 08:54:00 AM
but the program DOES erase the chip, but Cant flash it.
So now I am sitting with an emty chip and aa costumer sim expekting the box tomorrow
Post by: Lord Brice on August 26, 2003, 03:54:00 PM
Post by: BrianM on August 26, 2003, 04:22:00 PM
| QUOTE (Lord Brice @ Aug 27 2003, 12:47 AM) |
| MAJOR PROBELM!!!!! u people complainging about SYNC errors, or not being able to read and write have it made easily... i cant do ANYTHING!!!! the only thing my programmer does when i am running x2cable... is the command prompt just says "Unable to start drivers!" hell... maybe if i knew what was wrong i could get to where u guys are stuck at!!!! IF U KNOW MY PROBLEM, PLEASE HELP... AS I AM AS DISTRESSED AS ANYONE IS, IF NOT MORE.... |
Good grief - I told you it was in this post - there's a link to download the file that fixes the issue and everything. Did you even bother to read ALL the posts or are you just looking for a handout/someone to do it all for you? Who knows, you might come up with an error further down the line that you'll know the answer to already if you do read everything. It's not like this is a John Steinbeck book or anything ~ easy and quick to read.
Post by: LateraLex on August 26, 2003, 06:08:00 PM
Post by: feflicker on August 26, 2003, 10:00:00 PM
Post by: Fredb on August 27, 2003, 05:30:00 AM
sync error with x2cable
and error at location 00000h ...... with x2pro.
could this be the problem for most people? try and reply.
Does anyone know a program that can monitor the traffic on the LPT port?
Post by: UnrealEureca on August 27, 2003, 04:40:00 PM
Post by: BrianM on August 27, 2003, 06:15:00 PM
For the people in/near Atlanta, I'll be more than willing to help. I have a programmer and an xbox with EvoX loaded for hot-swapping if necessary.
Post by: UnrealEureca on August 27, 2003, 09:41:00 PM
Post by: UnrealEureca on August 28, 2003, 12:03:00 AM
Ok but here is what my problem was and how i got it to work while trying to flash this dam thing i kept pulling of and on the chip to test so what eventually happened was i pulled off the ground line off the adapter
so i pulled out my soldering iron and started to solder it back on i turned the board around and look at the solder points on the programmer where the lpt port is at there was a bridge from ground to some other point at first i was thinking dam maybe they meant to do that but i said f*** it it aint working anyway so i set the soldering iron on it and took of the bridge hooked it up tried x2pro didnt work then tried x2cable worked fine i erased the chiped first and then programmed it and seems to be working fine im at 60% now
so for you guys that cant get it to work youll never know it may have been a production prob check the solder points at the bottom of the programmer make sure none of them are bridged
Post by: tez_a on August 28, 2003, 01:49:00 PM
So remember if you keep getting errors on many machines maybe the programmer needs checking.
Post by: Good-vs-Evil on September 01, 2003, 01:49:00 PM
Post by: dignick on September 03, 2003, 09:30:00 AM
[EDIT: checked the flasher, nothing apparently wrong with it]
Post by: llewop on September 03, 2003, 02:06:00 PM
Post by: harleyrace on September 03, 2003, 10:16:00 PM
I brought 30 AppleX3 and only 17 worked, the rest seem dead, also had a X-killer that was being flashed with Evo-x and had a power cut 1/2 way through erasing bios, so that 1 is now dead.
Can these chips be flsahed with this programmer, or has anybody got any idea how i can flash these.
Post by: dignick on September 04, 2003, 07:00:00 AM
Post by: Copytech on September 07, 2003, 06:56:00 PM
It worked. Windows does somuch auto configuration on ports, who knows why it changed. 4 hrs later I'm back in business.Good luck all, hope it works for you.
Post by: GenEriq on September 09, 2003, 07:57:00 AM
I did notice one odd thing. When I was trimming some of my connections, I forgot to reconnect pin 9 from the DB25M to pin 1 of the 74LS244. When this connection was not made, the software no longer reported sync errors, but read everything as "0"s. I could use the X2cable software without any sync errors (which are present even if you run the software with NO programmer connected). I just thought this might give some of you more advanced electronics techies some insight as to what could be going on.
Thanks for any info/help!
Post by: GenEriq on September 09, 2003, 11:26:00 AM
Post by: GenEriq on September 10, 2003, 01:46:00 PM
Post by: Balthazar_The_Great on September 11, 2003, 11:00:00 AM
mad props to him !and second I was getting lots of sync error = F so unpluged the programmer and inspected the solder points by the printer port with a 4x magnifieing glass and there was lots of briged solder points so I scraped them off cleaned everything and pluged it back in and flashed my chip 100% no probs and no errors
hope that helps anyone out there thanks again Lerxst!-Matt
Post by: vidiware on September 21, 2003, 10:24:00 AM
Post by: bman on September 21, 2003, 06:32:00 PM
Post by: mcornbill on September 22, 2003, 04:38:00 AM
I usually find that on the first attempt at flashing with the programmer I get SYNC errors but after that it will go all the way without a hitch but at the very end of the verifying process it will say "error at location....".
Now this has happened to the last 4 chips I have flashed but they all seem to work fine in the box. It never happened when I used to have the programmer directly into the back of the PC but I have now got a parallel lead from the PC into a A/B switch box and then the programmer into one of the outputs of the switch box.
Cheers
Post by: skat on September 22, 2003, 06:32:00 PM
is there a place with the error codes listed somewhere ?
also when I try and wrote my bios with xecuter bios manager it writes all the way through and then gives me an error at 000000 [ 00] expected [09]
I have been through so much crap to get this thing to even the stage and my head is starting to hurt so if anyone can help I would really really apreciate it
Post by: KenCuz on September 23, 2003, 08:50:00 PM
Post by: Zim on September 25, 2003, 11:12:00 AM
Post by: C.Maggard on October 04, 2003, 03:49:00 PM
Post by: C.Maggard on October 04, 2003, 05:46:00 PM
Post by: lilpunju on October 12, 2003, 02:39:00 PM
i have a xbox v 1.0 , x2lite plus, and the x2lite programmer
When i try to flash the chip with the programmer, it results in frags...
the only time it doesnt frag is when i flash it with the ozxchip bios or the clean linux bios
but i tried it with X2 4977, and EvoX M7, and some others.. all.. fragg
but when i program it i always get the same error, regardless of what bios i use...
When i use the "x2cable i" command to get the info it comes up as...
Manufacturer Code: 01h Device Code: 91h
Security Bit: 00000000
not the 01 D5h im supposed to get..
-The programer is directly connected to my printer port
-the chip is on enable, unprotect, bank 1 or 2 (same)
-Powered by USB
I can, erase the chip (x2cable e) or read the bios from the chip (x2cable r) and theres no problem at all
however when i try to write, it goes all the way to 100% in around 800s
then it says:
Writing...Done. Time taken = 810s.
Error at location 00000h!
then i install the chip and, once again, fragville... unless its a clean bios
then i flashed it with the only bios that works, the cromwell, and i made a cdrw with the x2 4977 bios on it.. i tried flashing it through the CD, after it erased, flashed, and verified..it shut down.. then..what happen??
FRAG!
I spent like $80 for all this, someone pleasee help, ill greatly appreciate any help to get me through this! and tell me if im not making this clear enough or left out any details..
-MaNNu
Post by: capt_n_yayo on October 13, 2003, 09:29:00 PM
I wish that matrix programer worked on lites and pros that w/ be nice.
Post by: Murphster05 on October 26, 2003, 02:20:00 PM
I am using an Xbox V 1.0 with an xecutor 2.2 Lite Plus. May want to add something saying you don't need the ground and there is no flash protection removal on the chip...
I got an error that said :
Error at location 000FDh!
I don't know what that meant...but I read the new bios using the step to read Cromwell (if the chip comes pre-flashed) and it found x4977 on there just fine, so I just put the chip back in and booted up, it worked great. Thanks a ton.
PS - if anyone knows what that error means and thinks that there may be a problem with running the chip after getting that message....a heads up would be much appreciated
Post by: feflicker on October 29, 2003, 11:50:00 AM
| QUOTE |
| Hmmm, looks like x2.2 lites dont stand a chance at being flashed by that device. |
Confirmed here as well... My worst results have all been with 2.2's... I wish Team X-Ecuter would come out with a new programmer that works on all X2's and even X3. If it was stable, there would be some serious value in it. I would buy one for sure
Post by: alg20 on November 01, 2003, 12:22:00 AM
I've entered all the command, checks, etc all check out. No error codes.. NONE AT ALL. any help would greatly b appreciated............
Post by: jerome187 on November 20, 2003, 12:01:00 PM
Post by: DraftZero on November 22, 2003, 04:13:00 AM
Cries of JOY! I got my thing to finnally do something else other than "unable to start driver" or "SYNC ERROR 7"info:
OS: Win XP Pro
Bios: ECP + ECC port 378
Chip: X2.2 Lite+
BIOS: 4977
USB Power, no ground (Lite+ doesn't have)
I first tried compatibility settings win95 because the link for the WinLPC wasn't working and i couldnt' find it.... well that was NO HELP... gave me the SYNC ERROR 7 instead of "unable to start driver" so i finnally found WINLPC on http://www.ozxchip.com downloaded it... ran it... let it do its thing... then canceled out.... ran Command prompt with BACK TO ORIGINAL SETTINGS (not running win95)... went to the directory and did "x2cable i" to my amazment... the farking thing WORKED!
gave me:
"Manufacturer code..... Security Bit"
Started on Instruction #6... on the first page... the damn thing had an error... so i just reseated my chip and fitted it on again... worked! (noticed that the cables kinda pushed my chip just a lil bit...)
After Reading my bios.bin file... everything was good... so i just busted a x2cable w bios.bin and watched the new episodes of TMNT... about 20 min later i came back to my comp... and everything seems gravy.. no errors...
took my chip and installed to xbox. tried 4979.. bastard won't work.. .so i tried 4977.. worked like a charm.. after some sleep i will try to get 4979 working.... muahahhahahahaha.
well good luck!
NOTES:
Also some time during this process i checked the back of my Programmer for solder bridges... and i noticed that there were some solder all kinds of places.. cleaned it up.... (not expecting anything).
Post by: LateraLex on December 11, 2003, 08:02:00 PM
Post by: netwalkr101 on December 15, 2003, 03:52:00 AM
| QUOTE (DraftZero @ Nov 22 2003, 02:06 PM) |
| Cries of JOY! I got my thing to finnally do something else other than "unable to start driver" or "SYNC ERROR 7" info: OS: Win XP Pro Bios: ECP + ECC port 378 Chip: X2.2 Lite+ BIOS: 4977 USB Power, no ground (Lite+ doesn't have) I first tried compatibility settings win95 because the link for the WinLPC wasn't working and i couldnt' find it.... well that was NO HELP... gave me the SYNC ERROR 7 instead of "unable to start driver" so i finnally found WINLPC on http://www.ozxchip.com downloaded it... ran it... let it do its thing... then canceled out.... ran Command prompt with BACK TO ORIGINAL SETTINGS (not running win95)... went to the directory and did "x2cable i" to my amazment... the farking thing WORKED! gave me: "Manufacturer code..... Security Bit" Started on Instruction #6... on the first page... the damn thing had an error... so i just reseated my chip and fitted it on again... worked! (noticed that the cables kinda pushed my chip just a lil bit...) After Reading my bios.bin file... everything was good... so i just busted a x2cable w bios.bin and watched the new episodes of TMNT... about 20 min later i came back to my comp... and everything seems gravy.. no errors... took my chip and installed to xbox. tried 4979.. bastard won't work.. .so i tried 4977.. worked like a charm.. after some sleep i will try to get 4979 working.... muahahhahahahaha. well good luck! NOTES: Also some time during this process i checked the back of my Programmer for solder bridges... and i noticed that there were some solder all kinds of places.. cleaned it up.... (not expecting anything). |
All i can say is if you have this configuration it works!!! i just tried it last night. worked like a charm! this needs to be in a tutorial!!! I dont know why running "win_lpc" works but it took care of the "unable to start driver" problem. The thing to remember is when you run win lpc you will get another error!! but close it out and rerun "x2cable" you might get an error on the first try but the second will most likely work. I reflashed the chip 3 times with this method just to make sure and had flawless flashes every time. Kudos to Draftzero for finding this by either experience or luck!!!
Also one last tidbit i forgot to mention. If you dont want the likely hood of this happening again. When you prepare your bios then make sure that when you make your bios, to include the bios you plan to use in bank 1. And in bank 2 a version of the cromwell bios. So now once you have bank 1 regular bios and bank 2 cromwell. any time you need to reflash you can use a cd to flash instead of the programmer. Just make sure EVERY time you burn a flash cd that you put cromwell in your bank 2 so it will always be there to repeat this process again!!! Thanks again to EVERYBODY for your help and to Draftzero for getting me to this point!!!
Post by: Ubergeek on December 15, 2003, 05:57:00 AM
| QUOTE (jerome187 @ Nov 20 2003, 09:54 PM) |
| Great, X2.2 Lites cant be programed with this thing.... thats the only reason i got it. This is fucked and I hate xecutor's overpriced chips. |
x2 are programmed with an x2 programmer
its designed for the x2. hence it being called x2 programmer.
Post by: Ubergeek on December 15, 2003, 06:05:00 AM
Post by: Ubergeek on December 15, 2003, 06:00:00 AM
| QUOTE (LateraLex @ Dec 12 2003, 06:02 AM) |
| I just got my 2.3 programmer and I delighted to say it is JUST as crappy as the last one. I have no idea why I bought another one only to find I get SYNC7's on every machine I have tried so far. |
do you have the switch plugged in and set to unprotect
the programmer works just fine on boxes ive tested with
Post by: Ubergeek on December 15, 2003, 06:01:00 AM
| QUOTE (feflicker @ Oct 29 2003, 09:50 PM) | ||
Confirmed here as well... My worst results have all been with 2.2's... I wish Team X-Ecuter would come out with a new programmer that works on all X2's and even X3. If it was stable, there would be some serious value in it. I would buy one for sure |
it does work with all x2's
Post by: Ubergeek on December 15, 2003, 06:28:00 AM
| QUOTE (Fragzen @ Jul 8 2003, 03:39 PM) |
| Couple of things that should be added to this tutorial. 1. X2Cable must be run in Win95 / Win98 compatible mode. 2. X2Pro might work where X2Cable doesnt. Greeds |
1. no it doesnt
2. no it doesnt
Post by: Ubergeek on December 15, 2003, 06:22:00 AM
| QUOTE (Mr.187 @ Aug 12 2003, 10:30 AM) |
| great tut lerxst, worked first time, i was a bit scared wen i couldnt plug the groung wire 2 to my executer lite 2.2+ but it worked all the same. |
you dont actually need the ground wire
Post by: Ubergeek on December 15, 2003, 06:31:00 AM
| QUOTE (ukplum @ Jul 15 2003, 06:49 PM) |
| a 13 quid parallel cable. |
you shitting me ?
I pay $1 for my cables - they work great
Post by: tallone on December 15, 2003, 07:19:00 AM
Does anyone know the commands for x2pro?
Thanks
Post by: Ubergeek on December 15, 2003, 07:38:00 AM
hence it being called x2pro
Post by: Ubergeek on December 15, 2003, 07:39:00 AM
it works fine for both pro AND lite
Post by: LateraLex on December 15, 2003, 08:37:00 AM
Now I dont get SYNC=F errors when I do x2cable i
However now when I go x2cable r crom19.bin I get
SYNC=D
SYNC=F
SYNC=F
SYNC=6
SYNC=F
SYNC=F
SYNC=F
hmm
for 2.3's is it still crom19?
Post by: miggidy on December 15, 2003, 10:01:00 AM
Post by: miggidy on December 15, 2003, 09:55:00 AM
I was getting the same error messages as everyone else at home with my personal PC.
I hooked up the programmer with my office PC and what do you freakin know?
The son of a bitch finally worked. ( I use Win XP at home and Win2000 at work).
I was able to flash my XL 2.2 with ease.
Now does anyone know how to flash a 2.3 Lite with this programmer?
My programmer came without that PCB piece.
Post by: miggidy on December 15, 2003, 10:04:00 AM
Post by: LateraLex on December 15, 2003, 10:36:00 AM
| QUOTE (LateraLex @ Dec 15 2003, 12:37 PM) |
| for 2.3's is it still crom19? |
it looks like its x2cable r crom18.bin for the 2.3
Post by: Ubergeek on December 15, 2003, 11:24:00 AM
| QUOTE (miggidy @ Dec 15 2003, 07:57 PM) |
| Scratch that, the Console Corner just told me that the old programmer won't work for the 2.3 chips! Rats! I need to order the new one |
no you dont
we posted a fix on teamxecuter.com last week
also try use the x2 bios manager v2 beta 7 instead of the x2cable app. the one on xbox scene downloads doesnt even work for me
Post by: miggidy on December 15, 2003, 01:08:00 PM
| QUOTE (Ubergeek @ Dec 15 2003, 09:24 PM) | ||
no you dont we posted a fix on teamxecuter.com last week also try use the x2 bios manager v2 beta 7 instead of the x2cable app. the one on xbox scene downloads doesnt even work for me |
Whew!
Thanx bro, you just saved me a few buckaroos!
Post by: miggidy on December 15, 2003, 01:15:00 PM
| QUOTE (Ubergeek @ Dec 15 2003, 09:24 PM) | ||
no you dont we posted a fix on teamxecuter.com last week also try use the x2 bios manager v2 beta 7 instead of the x2cable app. the one on xbox scene downloads doesnt even work for me |
Damn I just checked TeamXecutor.com and it says I need a X2.3L adapter.
Do you know where I can find it?
Anyone?
Thanx for the help
Post by: HardEight on December 15, 2003, 04:36:00 PM
MY x2bm says
Error at flash address 0x000000
Read [00], Expecting [09]
This is with the programmer connected directly to my Laptop and a X2.2L
The Programmer recognizes the X2 and says its erasing the chip then goes to "writing 256kb" and says 50% FOREVER
Any Help addressing this?
Post by: @win on December 22, 2003, 03:26:00 AM
I searched the forum, but haven't found a solution to my sync probs.
I have a 2.2 (or 2.1) lite (cannot tell the difference) and I am trying to flash it with a programmer. When hooked up to my PC, is can read the bios fine, but when I try to erase or write the BIOS (with the swith set to unprotected), it gives me the following errors:
Erase:
D:X2cable>x2cable e
Erasing...Error: SYNC=1
Error: SYNC=8
Error: SYNC=1
Error: SYNC=1
Error: SYNC=8
Error: SYNC=1
Done. Time taken = 1s.
Write:
D:X2cable>x2cable w edwin.bin
Erasing...Error: SYNC=1
Error: SYNC=8
Error: SYNC=1
Error: SYNC=1
Error: SYNC=8
Error: SYNC=1
Done. Time taken = 1s.
Writing...Error: SYNC=1
Error: SYNC=8
Error: SYNC=1
Error: SYNC=1
Error: SYNC=8
Error: SYNC=1
Error: SYNC=1
Error: SYNC=8
Error: SYNC=1
and so on . . .
It looks like the LPT port is OK, because it can read OK. I tried it on 4 PC's already, and also changed the LPT type in the BIOS.
When I install and disable the mod-chip, it goes to M$ dash as expected, when I enable the chip FRAG's (3 x boot, then fails).
Is my d0 point bad ? Or the LPC points ? I checked them, but they seem OK. It looks like the chip is OK too, because I can read from it