Jump to content

XEcuter 2 3b Lite Install Diagram. 1.6 Compatibility?


Recommended Posts

Evening all i've got 2 2.3b Lites and one 2.6. Anybody got the install diagrams as I can't seem to find them only the 2.3b+. 


Also with my LPC Rebuild kit they should work for 1.6's as long as I flash a working bios / Cromwell before installing? As I've ran out of Aladdins and have a few consoles in need of work. 

Link to comment
Share on other sites

  • 2 months later...
1 hour ago, malarrya said:

I actually just removed this from my Xbox 1.0 a couple weeks ago and am looking to possibly eBay it. Any reason I should keep it?

Team Xecuter _ Xecuter 2.3B Lite Plus Install.pdf 929.68 kB · 1 download

Eh, if you’re on a 1.0 you can really get the same feature set besides write protect, which is still achievable with a switch, as is multibios on the 1MB flash chip. 

Having a chip around can always come in handy if your BIOS gets hosed for some reason though. 

Edited by Magicaldave
  • Like 1
Link to comment
Share on other sites

1 hour ago, Magicaldave said:

Eh, if you’re on a 1.0 you can really get the same feature set besides write protect, which is still achievable with a switch, as is multibios on the 1MB flash chip. 

Having a chip around can always come in handy if your BIOS gets hosed for some reason though. 

It wasn't making good contact with the board any longer. I think I tightened the screw down one too many times. It would cause the Xbox to power cycle 3 times then flash red. I never used the 2nd bank back in the day because I was too worried about screwing up the modchip. I actually just recently updated it with the latest Xecuter BIOS for it but the TSOP is soooo much better. 

  • Like 1
Link to comment
Share on other sites

  • 9 months later...

That's for the Xecuter 2.6 the OP here asked about. XpertXP should have made it clear he's asking about the Xecuter 2.3B Lite and specifically a wired install rather than pogo pin or a v1.0/v1.1 MB.

I assume the wired install is for the d0 connection which, from the PDF, sounds like a very odd way of doing things.

These screenshots are direct from the PDF and might help:-




Link to comment
Share on other sites

I don't have an Xecuter 2.3B Lite plus with pogo pins but I suspect the pin header on it may be a direct connection to the pogo pins.  

I believe it was used to connect to an external programmer so they may not be.  Hard to find specifics on it.

the only installation instructions released by Team Xecuter were for doing the pogo pin install that's how the chip was built.

You could solder a wire to the top of each pogo pin and solder it to the associated pin of the LPC Debug header port on the motherboard.  Where and how do you plan to locate the modchip so it doesn't make an electrical contact with something it should not.

What version Xbox?  If a 1.6, it was not intended to be installed in one.  There was no 1.6 Xbox when it was released.  An LPC rebuild is required and most likely an LFRAME# trace cut by the Xyclops chip which will disable booting from the the stock BIOS.  And, D0 connection to ???.

Link to comment
Share on other sites

XpertXP is talking about a v1.0/v1.1 and I assume too, after reading the PDF manual , that the wired solution is similar to what you've described but maybe just wiring the appropriate d0 pogo pin to the contact point on the MB.

I do not really see the point of wiring the LPC pogos instead unless there is some other mounting position/solution being proposed.

Using a pointy d0 pogo pin to line up with the small contact point underneath the chip rather than solder it in is a rather odd way of doing things. The PDF manual even warns installers that poor alignment could damage the MB, that the chip might not work if the one retaining screw is not tightened up just the right amount and that screw must be used with a spacing washer to keep the chip from fouling the MB, at the right level for the d0 pogo and ground it too.

The later Xecuter chips were mounted differently for good reason.  

Edited by HDShadow
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By Johny white
      I'm about to install this spi2par2019 to use with my open xenium. I've soldered a single row pin header to the spi2par2019, can I solder the other side directly to the lcd screen? The reason I'm asking is that I can only see pictures of Rezze doing this while everone else seemed to use wires to connect to the LCD it self!!!!

    • By mandalore30
      Hi I recently got a non working crystal xbox(1.6) for cheap, I already have a tsop 1.4 and was wondering if I can put all it's components(mobo,psu, dvd etc) into the crystal case. 
    • By HDShadow
      I've had a v1.6 Xbox with a pro-fitted Xecuter 2.6CE since 2005 and its been pretty much perfect until recently.
      On two or three occasions its refused to boot either via the Power button or the Eject/Close button. I get a green/red flashing LED typically indicating a hardware error. Sometimes it does that once and then shutdown, others times it frags.
      However I found that if I shutdown, switch the chip off, boot to Error 5 (unlocked HDD) then switch off and reboot with the chip back on everything is back to normal.
      But yesterday I noticed something else weird: the chip has two 512K banks with the originally supplied custom EvoX BIOS on both. The only difference between them is Bank 1 has the EvoX logo and Bank 2 doesn't. I usually have it set to the EvoX logo one but now it has swapped to the non-logo version on boot. It doesn't seem to matter whether I switch banks or not.
      You might think a connection problem with the switch array ie. it is stuck on Bank 2 but, here's the weird thing: if I Reboot from my Unleash main dash or IGR the EvoX logo version BIOS appears to be used.
      Never heard/read about anything like this - any ideas what is going on? 

Board Life Status

Board startup date: April 23, 2017 12:45:48
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.