KaosEngineer

No, I just included a picture to show the top and bottom trace layers, top silkscreen and board outline. Easier for the OP to see the connections. Pin 1 is the square pad of the 2x5 connector and right-most pin of the 1x9 pin connector on the bottom left of the PCB. J1 - 2x5 connector pin numbers 1 0 8 6 4 2 0 0 0 0 0 0 0 0 0 # <--square pad 9 7 5 3 1 J3 - 1x9 connector pin numbers 9 8 7 6 5 4 3 2 1

Disconnect the wire soldered to BT from the power button. Connect a new wire from BT to ground for always-on mode.

Oh, I see, there's the weird thing about the Aladdin chips. To enable the chip, you have to press and hold the power button for ~1 second. If the console reboots, the modchip does not see a long power button press (modchip disabled) and the stock BIOS boots which leads to the stock dashboard loading.

Hexen takes about a minute before the menu appears. The Eject ring LEDs will change to RED to indicate that HeXEn is loading but the screen will not change until that minute of delay. Leave it alone, wait patiently and see what happens. If the menu has not appeared after waiting 2-5 minutes, somethings wrong.

The top 2 pin connector on the right side of the power/eject board - top pin connects to power button signal (pin 2) and the bottom pin connects to eject button signal (pin 4).

Was that your post - N136lph03n1x - aka xbmc4xbox's looney bin jim? Update: Can you post more pictures of it?

I'm not sure which pin of the 2 pin cable going to the X3 modchip is connected to power and eject. If it doesn't function as expected, unsolder them and swap the pin each connects to and resolder. Attached is the x3ce installation manual in PDF format. x3ce.pdf

The 1x9 pin connector of the front panel switch/LED board (right side of the picture) can be accessed through a slot in the RF shielding. The second and fourth pins from the bottom are the power and eject buttons respectively as seen below. Front panel LED/switchboard (component side) and motherboard connector pinout. Source: http://modzone.dk/forums/showthread.php?threadid=252

Here's the entire first post again with the black text color changed.

Is that the X5 Xtender case mod? Someone else was asking about it on one of the Xbox sites I frequent. Don't recall which they only had 1 small picture of it. Maybe it was an old post too as I use the Wayback Machine a lot to try and track down old Xbox modding scene info. Update: Found the post at xbmc4xbox.org.uk from three years ago - x5 Xtender

For a direct connection, no gateway IP address even has to be set. Devices on the same subnet (IP/Subnet Mask: 192.168.1.0/255.255.255.0) don't use it. These devices can communicate with each other directly. The gateway address is only used to forward packets to a different subnet through a router/gateway (e.g., 192.168.1.0 to 192.168.2.0. These are different subnets.) or if sending data across the Internet.

Those values all look correct. Are you trying to use FileZilla's Quick Connect boxes to login? They try to connect to an FTP server securely which the Xbox's FTP server does not support. Create a Site Manager entry for the connection and make sure the Encryption entry is set to Only use plain FTP (insecure). Then set the number of simultaneous connections to 1:

They are on the HeXEn 2018 disc and the Xbox Softmodding Tool Extras Disc too.

I'm not sure that the TruHeXEn 2019 (Is that the one?) release's M8plus dot bin file has the DVD check disabled. Forlorn Pengiun's HeXEn 2018 release does. It also has the LBA48 v3 patch applied that the official Evox release does not.

Softmodded systems require leaving the main controller board of the DVD drive connected to the IDE bus and the Xbox's DVD power/control signal cable. They are still booting the stock BIOS that checks for the DVD drive during the bootup procedure. The softmod is enabled after the normal boot procedure completes and the MS dashboard starts. Somewhere in there. But, its after all the hardware checks have been completed. If no DVD drive is connected on a softmodded system, you will see an error screen - one indicating a DVD error - 10, 11 or 12 not exactly which. Hardmodded consoles, either TSOP mod/reflash or a modchip installed, when booting a BIOS with the DVD check disabled do not require the DVD drive's PCB to be connected to the console. The entire drive can be removed.

You need to break all three grounds; thus, the 3-pole switch. Not a single-pole switch. Single throw means each pole will either be open or closed. The state of all three poles the same - either all open or all closed. But, ground is ground, isn't it? Not sure why there are three separate wires unless for the current rating of the wire gauge used. Shouldn't a SPST switch work too? I'd not heard anything about one BIOS having more or less game support than another.

Yes, break ALL the ground connections - there are 3. Use a 3PST (3-pole single throw) switch?

There's a Youtube video series by Surly Sot Gamer Club showing a daily series of updates to their/his Xbox. On Day 16 he's working on no DVD operations but didn't get much accomplished other than causing more problems. On Day 17, he continues with HDD partitioning and no DVD operation testing. Using iND-BiOS 5003.67 or is it really 5004.67. The NMS TSOP flasher he used shows both values the first as the Kernel version with a BIOS name of the second. A misconfiguration of the MD5 hashes used to ID the BIOS? The console DOES boot without the DVD drive attached and NO DVD Simulator plug is connected. He's completely disconnected both the IDE cable and DVD power cable from the DVD drive. There does seem to be a long pause - 10-14 seconds of a blank screen - after the flubber animation ends and the dashboard shows up when the DVD drive is disconnected though. Updated correct Days for Surly Sot Gamer Club's YouTube videos and added links to them.

What's about pins 2, 10, 1 and 9? Those pins supply power to the DVD drive. Update: Oh, I see. I missed your post on powering on/off the DVD drive with a switch. You need to make this so called DVD Simulator jumper to plug into the motherboar's DVD power connector to pull HIGH the CD_RDY and TRAY_IN signals routed to the SMC so it knows the drive is ready. Here's one such plug I found at xbmc4xbox.org.uk - https://www.xbmc4xbox.org.uk/forum/viewtopic.php?f=13&t=373#p13212 However, instead of a wire to directly connect from 5V to B and 5V to D, I would use a 10KOhm resistor.

I think the BIOS's DVD check looks at the IDE bus for a SLAVE Xbox DVD drive attached. It doesn't skip the assertion check of CD_RDY and TRAY_IN signals done by the System Management Controller (SMC, a PIC processor in v1.0-1.5 or custom Xyclops chip in v1.6 Xboxes).

I've never done this mod; however, I understand the basics. You need to have a BIOS flashed to the TSOP/modchip that disables the DVD check on power on. And, I think you also need to make a properly configured connector to plug into the DVD power connector on the motherboard. This is the image of the connector pinout I've seen but it only has 12 pins not the 14 present on the motherboard. The next two 13 and 14 have no connections to the DVD drive though so I guess the original author just left them off. TRAY_IN and CD_RDY need to be tied to Updated: hmm, either Ground (GND) or +5V to signal to the System Management Controller (PIC processor v1.0-1.5 consoles) that the tray is closed and the drive is ready. I don't know if TRAY_IN and CD_RDY are active low or active high signals. I'll have to see what I can find again. I've seen a slim build log on the Internet of someone that removed their DVD drive and showed the jumper plug they had made. Update: Looks like they are active HIGH so they need to be tied to +5Vdc. Although I'd probably use a pull-up resistor of 10KOhm for each from 5Vdc to the signal pin. (2 resistors one for each signal to +5Vdc). +5Vdc(pin 2) -\/\/\- CD_RDY(pin 6) and +5Vdc(pin 10) -\/\/\- TRAY_IN(pin 7) -\/\/\- is my ASCII representation for a resistor. Use a 10KOhm 1/4watt. Probably could be a much wattage rated resistor (1/8 watt).

The Extras Disc ISO is on google drive, not in the github repo - at least not anymore. Try here in Build v1.1.6/Extras Disc for the disc image.

U6F1 on a v1.0 - v1.5 motherboard. Not present on a 1.6 motherboard. From the little bit I've seen / read about it, MS removed it to save some money as there were hardly any overheating problems with the console.

Those are a bit old and can be easily updated. Dashboard RemoteX is also known as Evoxdash. The latest release is +3935. A slight naming change from the previous 1.8.nnnn that dropped 1.8 in front of the nnnn value. BIOS Update X2 4981.67, M8plus, iND-BiOS 5003.67 or iND-BiOS Feb-11-05 Beta (aka 5004) are most of the latest BIOSes to use with your modchip. Evoxdash can be used to flash a new BIOS to the chip. All of these are on the HeXEn 2018 disc which after extracting and burning the image to DVD-R media can be booted and used to update your modchip's BIOS as well. Dashboard Update There are other dashboards considered a better choice as they contain a built-in File Manager - UnleashX 0.39.0222A Build 572 and 0.39.0528A Build 584 are the latest releases. Build 584 has an FTP server bug that adds extraneous date string preceding the root listing drive letters. Rocky5 has released a hex edit patched version of it to take care of that and a couple other bugs. A couple of other replacement dashboards include XBMC4Xbox v3.5.3 and XBMC-emustation .

What kernel/BIOS is currently flashed to the modchip? Which replacement dashboard is installed?