KaosEngineer

Good for you saving that information. However, I don't know that the X2 4983.67 BIOS will work to change the partitions to use 64KB clusters necessary to properly format the two extended partitions of a 2TB hard drive. Partitions 6 and 7 must use 64KB clusters. XBPartitioner (XBP) v1.3 must be used to set the partitions cluster size to 64KBs instead of 16KBs. But, I believe, XBP v1.3 will complain that no LBA48 support is found. At least, not the patch level it is looking for - v2 or greater. You will need to use a different BIOS - M8plus F and G on the Hexen 2019 disc, X2 5035 or iND-BiOS 5004.67. But, let's first get you back to where you were: You will need to download a copy of the X2 4983 BIOS archive to your PC: X2.4983.BIOS.rar Extract the contents and post back here when ready to proceed.

Great news! You can reflash a different BIOS to the TSOP using the XBlastOS. Do you know which BIOS was flashed to the TSOP before the XBlast OS upgrade?

How's your console modded? Or, better how was it modded? If a modchip is installed or TSOP reflashed (, your nephew ingeniously figured out how to flash a different BIOS to it. Edit: You need to do the same. Replace the XBlast OS with the original BIOS you had flashed to the modchip/TSOP. P.S. I really should read all of the text - How modded? - TSOP reflash. You stated that from the beginning.

Or, if they did, they are not releasing them.

Yeah, that's the problem no one seems to have backed up the source files from http://svn.sickmods.net/. The Wayback Machine has the directory listing and a couple of the files, pulsevu2.aps and startuptest.c, but not all of the files listed below: pulsevu2 - Revision 2: / builds/ defines.h gpl.txt interrupts.c luts.h modes.h pulsevu2.aps pulsevu2.c pulsevu2.h scilab/ startuptest.c startuptest.h stddef.h Powered by Subversion version 1.5.1 (r32289). or the builds/ files (only the listing of the files) or the scilab/ files (nothing captured): pulsevu2 - Revision 2: /builds .. pulsevu2_v1000.hex pulsevu2vx_v1000.hex smfader_v1000.hex Powered by Subversion version 1.5.1 (r32289).

Was XBlast OS on the hard drive? Was the Hexen Disk in the DVD drive? Red/Yellow flashing can indicate a RAM error. However, the XBlast OS changes the Eject ring to flashing red/yellow when it runs. Did you power cycle the console? All should be good after a restart. Edit: Updated content above as I just ran XBlast OS on my console. XBlast OS does change the Eject ring to flashing red/orange. Use the D-pad to move right to the Settings icon, press (A) then down to the Power menu > Reboot highlighted and press (A). Or, simply power cycle the console using the front panel power button.

The configuration EEPROM is on the Xbox motherboard. It is an 8-pin surface mount 2048-bit serial EEPROM. It holds 256 bytes of configuration information. The hard drive has stored on it the ATA Security password the Xbox computed based on the configuration EEPROM's HDDKey, the hard drive model and serial number. You either need to update the configuration EEPROM's encrypted and signed data by editing a copy of the eeprom.bin backup (only edit a copy of it not the original) with LiveInfo_Beta_3-Xbox_v1.6-Yoshihiro.rar to change the HDDKey to 0 (NULL it) instead of the original unique value. Save the updated NULL'd eeprom.bin file and write it to the Xbox's configuration EEPROM. You can use a serial EEPROM reader/writer, PC with a 9-pin serial port and PonyProg software or a Raspberry Pi and PiPROM software. Or, unlock then relock the hard drive with the password computed from NULLing the HDDkey of your original eeprom.bin backup. This requires some manual intervention on your part, not using the scripts of XboxHDM23USB, to unlock then lock the hard drive using smartctl.exe version 6.2 from XboxHDM23USB Beta 2 or 3 to do so.

Which drive: the hard drive or the DVD drive? The hard drive does spin non-stop. Your console was modded? If so, how so: soft or hard mod installed?

It was on xbox-skins.net.

You can find pre-wired 3-pin JST connectors that will do the job. The wire colors may be different but if you connect the correct wire to the LAN, HDD and D0 pads you'll be set. For example: 10sets Mini Micro JST XH2.54mm 3-Pin Connector Plug With Wire Cable 150mm (US $0.99 + $1.50 S+H) This listing is only one example there are many more sellers on eBay, etc. I believe that's the correct connector. Let me do a little more research to verify if that is the connector type. I'm not sure if 150mm (15 cm) wire length is enough. You also don't have the single RED wire RED connector used to provide 5Vdc from the alternate source for a 1.6 version Xbox.

Welcome to OGXbox.com. We certainly will appreciate any help you can give our members. Mod it or lose it, KaosEngineer

You were asking about this skin? UnleashX - Farscape.zip

Which brand and model 2.5" hard drive? Is it IDE or SATA? If SATA which IDE-to-SATA adapter are you using? If you don't use a Molex power splitter, how are you powering the IDE-to-SATA adapter if a SATA hard drive and/or the hard drive itself?

The problem is the stock BIOS does not support a hard drive over 137GB (123GB to F) the other space is allocated to the stock Xbox partitions. The Xbox Softmodding Tool softmod does support drives up to 2TBs; however, an XBPartitioner partition table has to be present on the hard drive to use all the space on drives larger than 137GBs. Before cloning, I believe you could have ran the XBP Table Writer application (found in the Chimp261812's repository under the E Partition folder at github.com) to write an XBPartitioner partition table to the drive. Or after cloning, ran it then rebooted. I've not tested either option though to verify it works.

All Xbox's have different data stored in the configuration EEPROM. If you are needing it to simply lock the hard drive on a PC using XboxHMD23USB Beta 2 or 3 or other DOS locking software for the Xbox that uses eeprom.bin to compute the locking password, you can create one for your Xbox version with: LiveInfo_Beta_3-Xbox_v1.6-Yoshihiro.rar P.S. There's also a method to compute the locking password for the particular hard drive knowing the HDDKey value (NULL = 0), its model and serial number string. I need to find the link again to the web page describing the process and the software that is used to compute it.

Okay, I'll add a copy of the post I provided the link to that paul_phil made on team-xecuter.com's web site on Jun 22, 2005: Source: https://team-xecuter.com/community/threads/pin-outs-for-x2-6ce-remote-switch.20976/post-196737

Check this post at team-xecuter.com: https://team-xecuter.com/community/threads/pin-outs-for-x2-6ce-remote-switch.20976/post-196737 The info there's for a X2.6CE. Update 20220530 - NOTE: The above link no longer works since Team Xecuter's web site has been seized by the U.S. government. However, there is an archived copy at archive.org's Wayback Machine. Scroll down to post #6 by paul_phil on the following webpage: Pin outs for X2.6CE remote switch | Team-Xecuter Community (archive.org) I've included the text from paul_phil's post below:

Depends on the softmod used. As long as it has LBA48 patch v3 support like Rocky5's Xbox Softmodding Tool does then YES.

If you have the X3 BIOS installed on the X3 modchip, you can use the X3 Config Live > Disk Tools menu options to format a new hard drive. And, FTP to the console, username: x3 and password: x3, to install a replacement dashboard to it. The IP address to FTP to is shown on the X3 Config Live screen: For more information on using the X3 modchip and BIOS, see: http://x3.bustedchain.com. Note: The X3 BIOS will not properly format a new hard drive's extended partitions if they are over 256GBs in size. I believe it only supports formatting the extended partitions using 16KB clusters, not 32KB required for partitions >256GBs up to 512GB. or 64KB clsuters required for partitions >512GBs to 1,024GBs (1TB). If the hard drive is too big, you will need to reformat the extended partitions with XBPartitoner v1.3 before you store data to them. Once too much is written, the partition(s) will become corrupted. Enable the Use Saved Partition Table option in the New Hard Drive Upgrade submenu settings so you can use the larger than 256GB extended partitions.

I think it uses NKPatcher code, so you can place a file (upload it) to the Xbox's E drive to disable the virtual EEPROM. E:\NKP11\eeprom_off.bin (if the NKP11 folder doesn't exist, create it.) It might need to be in the root of the E drive instead of in the NKP11 subfolder. eeprom_off.bin is an empty file. NKPatcher code looks for a file of that name to disable the softmod's virtual EEPROM use. After uploading the file, reboot the console. It's presence should turn off the virtual EEPROM so any changes made by tools to the EEPROM settings such as EnigmaH does to switch video regions. Therefore, the app can now actually write to the hardware instead of the in-memory copy (virtual) EEPROM.

From the factory, each Xbox has a unique HDDKey stored in the configuration EEPROM on the motherboard. This HDDKey along with each hard drive's Model number and serial number are used to generate a unique locking password for each hard drive locked for the Xbox it is installed in. Thus, if this hard drive was installed in a different Xbox, the password is different. A change in the HDDKey between the two Xboxes. And, the password generated for a different model and serial number hard drive will be different for a particular Xbox it is installed in. The Xbox's BIOS computes the correct password to unlock the hard drive each time the console boots. It reads the HDDKey from the configuration EEPROM and the hard drive's model and serial number to compute the correct password to send to the hard drive to unlock it to gain access to the files stored on it.

So, where's the flashing a BIOS occur? You only mention installing, removing then reinstalling a softmod?

How is your console modded? Soft or hard mod? Must be softmodded with a virtual EEPROM (copy in memory) enabled. If softmodded, which softmod package was used: Xbox Softmodding Tool or Softmod Installer Deluxe, etc.? If you used the Xbox Softmodding Tool, use the NKPatcher Settings app to change the region. It will modify the real EEPROM chip on the motherboard instead of the virtual EEPROM in memory that gets reset when you power cycle the console.

Check @N64 freak's subforum PM him your query to check availability.

Try https://reddit.com/r/xboxmodding/