KaosEngineer

This forum is for the original Xbox, not later Xbox 360 or Xbox One models.

The configuration EEPROM has no information about the hard drive installed in the Xbox it came from. Where are you seeing such information? LiveInfo shows the hard drive information for the hard drive attached to your old PC's IDE ports.

I'm not sure how you flashed the X2 4983.67 BIOS using HeXEn 2018. It is not on the disc.

There does seem to be a problem with the X2, edit - not X3 as posted originally, 4981 and 4983 BIOSes and support for LBA48 v3. It's not supported! Do not use either of these BIOS versions for huge hard drives that would use a partition of > 512GBs. With the .06 version F limited to <512GBs. Or with the .67 version F will be limited to ~130GBs and G takes the rest up to 512GBs (32KB cluster size). [NOTE: These are my current understandings. More research needs to be done on the particulars of using the X2 4981 or 4983 BIOSes. They definitely DO NOT read a partition table from the hard drive. LBA48 v0 support only.] The minimum version release of an X2 BIOS that supports LBA48 v3 is X2 5035. From my current research, the following BIOSes: 4981.06_256k.bin 4981.06_256k.bin x2_4983.06_256k.bin x2_4983.67_256k.bin cannot [edit: easily] be patched to add the latest LBA48 v3 support. Edit: There is no a patch for them. Note: Team Xecuter's X2 4981 and 4983 BIOSes only support v1.0-1.5 Xbox consoles. Do NOT flash them to a modchip installed in a v1.6 console. FIX Use a different BIOS! M8plus from HeXEn 2018 that's patched with LBA48 v3 support. Or, X2 5035_vOld_512KB.bin which however is not on the HeXEn 2018 disc Or, iND-BiOS 5003.67 which is on the HeXEn 2018 disc. Note: Team Xecuter's distribution archive contains both a v1.0-1.5 - X2 5035_vOld_512KB.bin and a v1.6 - x2_5035_v16plus_512k.bin BIOS. The default LBA48 configuration of these BIOSes is set to .06 - F gets all. However, the LBA48 patch in these BIOSes is v3. From the X2.5035.rar archive's lba48.txt file: lba48 partition modes: 0 = standard partitions 1 = F: gets all (Default) 2 = F: up to 137gb, G: gets rest 3 = F: up to 137gb, no G: You have to patch 0,1,2 or 3 value at offset 0x1b04 (if you wanna hex dit manually) However there are tools for lba48 patching and ini file creation - they can be found here: http://home.alltel.net/nghtshd/x2ool.html http://x-projects.xbox-scene.com/ //end lba48.txt However, if you write an Xbox partition table to the hard drive with XBPartitioner v1.3, the table's configuration overrides the BIOS's default 06 configuration.

If it complains, it must not be. I do know that the EvoX M8plus BIOSes have been patched with the latest LBA48 patch. However, I thought the X2 BIOSes already had the latest LBA48 patch from the previous 2017 release that were used in the 2018 HeXEn update. I'll do a bit of testing and post my results.

What other CD did you use? Nothing from your description of the steps performed should now be giving you error 16. Unless that OTHER CD removed the MS dashboard files from the C drive.

Yes, a standard PC cable doesn't fit with cable connectors as the locations they are meant to be installed at. Blue is to be the host (motherboard), Grey - IDE SLAVE device (DVD) and Black - IDE MASTER device (Hard drive). However, in the Xbox, the cable is flipped end-over-end so black connects to the motherboard and blue to the hard drive/IDE-to-SATA adapter. Doing so defeats the cable's built-in CABLE SELECT function; therefore, you have to set the hard drive to MASTER instead of Cable Select.

Which color ends did you connect to the motherboard and hard drive? If you have the ends wrong, Cable Select will no longer work and you have to set the hard drive or IDE-to-SATA adapter as MASTER.

The Advanced AV pack is not the same thing as the High Definition AV pack. There's not an Advanced High Definition AV Pack. The Advanced AV Pack is still composite video but also includes an S-video output. It does not provide high definition component video out. So, which one did you find: High Definition AV Pack, or Advanced AV Pack?

Which softmod package did you use?

It's the softmod that's causing the problem not the UnleashX dashboard. When booting, the softmod checks for the date/time value to be between a known min and max value. If the date/time is not within that range, the clock is set to the min value. Backup your C drive using FTP then upgrade the old SID softmod to Rocky5's Xbox Softmodding Tool using the Build v1.1.7 / Installer Variants / Quick Upgrade.zip content. Instructions inside the archive's Read Me.txt file on how to use it. The C drive will no longer have the MS dashboard available to run from it. You can upload a clean file set of the MS dashboard version 5960 back to the C drive or use the Xbox Softmodding Tool Extras Disc to re-install it.

How is the Aladdin chip configured/installed? Does it have the BT pad wired to the power button signal from the front panel or is it connected to a ground pad on the modchip for always on mode?

Which EvoX BIOS version? Must be a very old one that doesn't have the Err16 patch in it.

So, you are using a high-definition AV pack or cable with Red/Green/Blue component video signals and Red/White analog audio connected to your TV? Try the following: Press and hold the Left trigger, right trigger, and both analog stick buttons. The normally displayed 480i dashboard will switch to 480p output while using the Xbox High Definition AV Pack or cable. Repeat the button combo to toggle between the two resolutions: 480i and 480p.

xplorer360 isn't going to work with SATA ports - USB or IDE only. And, not sure if a USB-to-IDE adapter will be seen. I've not used it to access an Xbox hard drives content. USB is used for thumbdrives to add the softmod game saves to be copied to the Xbox and run an original exploited game. You can use a 64-bit Windows PC with a compatible USB-to-HDD interface adapter and XboxHDM23USB Beta 3 to prepare a hot-swapped drive (easier if you had the eeprom.bin backup) with a bootable no-original-game-disc-required Xbox Softmodding Tool installer. (Do not mess with the files already present in the HDD_files folder.)

Never heard of such a problem. Write the flash.bin file for XeniumOS 2.3.1 that has the recovery BIOS using xenium-tools.xbe. Check this forum: On another topic XeniumOS hangs without DVD drive https://github.com/Ryzee119/OpenXenium/issues/3

No the problem is with the softmod you have installed - SID (Softmod Installer Deluxe). It checks the system time for a maximum date/time value of midnight 6 June 2019. If the console's date is after date/time, it sets the clock to a default minimum value which I believe is midnight 4 March 2007.

Archival ISO's (those dual-layer disc images with Redump-certified MD5 hashes) can have the XDVDFS portion extracted with XDVDMulleter Beta 10.2. Redump does not provide the actual disc images only information to check the validity of original media archival rips.

NO, JTAG is not used to fix the OS portion of the OpenXenium modchip. The flash.bin BIOS/OS of the modchip and the openxenium.svf file for the FPGA/CPLD are two entirely different types of code for the OpenXenium modchip. (FPGA = field programmable gate array. CPLD = complex programmable logic device.) flash.bin contains the Xenium OS that controls the modchip. Written to the OpenXenium modchip's 2MB flash memory chip via the low-pin count (LPC) debug port bus. openxenium.svf is the firmware loaded to the CPLD. Written to the CPLD of the OpenXenium modchip via the JTAG port on the modchip. Not what you want to use to recover from wiping the XeniumOS from the modchip's flash memory chip. If you wiped out the Xenium OS and if the flash.bin originally written to the modchip contained the recovery BIOS section, you can enable the recovery mode of the chip and reflash the Xenium OS 2.3.1 to the chip. Or, if not, more about second recovery method later. From Ryzee119's OpenXenium README.md at github.com: If you bridge the two recovery pins on power up, it will attempt to boot the XeniumOS recovery BIOS if available. This functions the same as a genuine Xenium modchip. For more details on the use of the recovery mode, read the Xenium OS 2.0 User Manual. The original Xenium modchip had a switch to enable recovery mode. Edit: Oops, sorry, there's not much about using the recovery mode in the Xenium OS 2.0 User Manual. It's in the Xenium-OS Update Manual. Now, more on the second recovery method mentioned earlier: If you have another hard modded Xbox (or another working modchip to install into and boot this console) after booting into a replacement dashboard, you can hot-swap the modchip and write the flash.bin file to the OpenXenium modchip by running the Xbox application xenium-tools.xbe available in the releases section at the OpenXenium github.com site.

This video's a bit old but the steps to softmod are the same. The current version of Rocky5's Xbox Softmodding Tool is Build v1.1.7.

Are you sure the D0 wire from the modchip is connected to the correct side of the cut/resistor you added to repair the LFRAME# trace cut?

One reason the modchip may have been installed is because a TSOP reflash attempt failed and the console would no longer boot. Installation of the modchip was required to get the console working again.

L-shaped? Can you post a picture of it. Thanks.

The X2 BIOSes don't have a Config Live menu . It's only the X3 BIOSes that do. And, the X3 BIOS Build 3294 is the latest X3 BIOS ever released by Team Xecuter. You had nothing to upgrade to.

After copying the two softmod game save folders, one for the game to exploit it and the softmod installer folder itself, to the Xbox's hard drive before booting the game and trying to install it, power cycle the console.