Jump to content
OGXbox.com

KaosEngineer

Moderators
  • Posts

    4,859
  • Joined

  • Last visited

  • Days Won

    456

Everything posted by KaosEngineer

  1. 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.
  2. 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.
  3. 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
  4. 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:
  5. Depends on the softmod used. As long as it has LBA48 patch v3 support like Rocky5's Xbox Softmodding Tool does then YES.
  6. 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.
  7. 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.
  8. 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.
  9. So, where's the flashing a BIOS occur? You only mention installing, removing then reinstalling a softmod?
  10. 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.
  11. Check @N64 freak's subforum PM him your query to check availability.
  12. Try https://reddit.com/r/xboxmodding/
  13. This forum is for the original Xbox, not later Xbox 360 or Xbox One models.
  14. 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.
  15. I'm not sure how you flashed the X2 4983.67 BIOS using HeXEn 2018. It is not on the disc.
  16. 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.
  17. 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.
  18. KaosEngineer

    Error 16

    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.
  19. 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.
  20. 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.
  21. 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?
  22. KaosEngineer

    Error 16

    Which softmod package did you use?
  23. 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.
  24. KaosEngineer

    Error 16

    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?
  25. KaosEngineer

    Error 16

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

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.