KaosEngineer

Is the 5Vdc standby voltage level present on the motherboard? (Orange wires) I believe the Blue connection in the STB column is incorrect. It too will be 0 Vdc until the power supply turns on.

FTP the BIOS dot bin file into the subfolder BIOS where evoxdash's XBE file is running from (e.g. C:\evoxdash.xbe create a C:\BIOS subfolder and upload the dot bin file there). I believe you can flash a Matrix modchip using Evox but I've never had one and it has been years since I've looked into flashing one of them.

In the folder where XBMC's default.xbe file is located. While XBMC is running, it creates a mapped drive to that folder named Q:. It should be in there.

The BIOS flashed to your X2 modchip has a diffferent location programmed into its boot order list than where the dashboard is installed on your hard drive. If the three user-defined dashboards are not found, the stock dashboard is loaded from the C drive - C:\xboxdash.xbe. Originally X2 BIOSes had their boot order list set to: C:\evoxdash.xbe C:\avalaunch.xbe C:\nexgen.xbe Over the years devs of new install discs have changed the boot order list entries.

It doesn't have to be locked with a hacked BIOS. However, if locked, the hacked BIOS will unlock it.

It is a 2Kbit serial EEPROM. The Xbox's configuration EEPROM 256 bytes of data are stored in it. See: EEPROM - xboxdevwiki Edit: Microchip's 24LC02 in an 8-pin surface mount package. 24AA02/24LC02B/24FC02 2K I2C Serial EEPROM (microchip.com)

That chip, U7D1, is the 2Kbit serial EEPROM - configuration EEPROM (256x8 bits) on Xbox v1.6 revision motherboards.

I suggest trying the DOS command-line tool included with XboxHDM23USB - smartctl.exe - to unlock the hard drive. Instead of using the menu from XboxHDM23USB, open a Run as Administrator cmd.exe Window to manually key-in the command to execute the application - smartctl.exe - directly. At the command prompt, run the application with the correct options to access the USB adapter attached Xbox hard drive. First, find the correct device name Windows assigned to the Xbox hard drive you want to unlock. To do so, enter the following command at the prompt: wmic diskdrive get model,name Example output: Model Name HGST HTS545050A7E680 \\.\PHYSICALDRIVE0 SanDisk SDSSDH3 1T02 \\.\PHYSICALDRIVE1 WDC WD10 02FBYS-02A6B0 USB Device \\.\PHYSICALDRIVE2 Here Windows has assigned the Xbox hard drive the device name: \\.\PHYSICALDRIVE2 However, smartctl.exe uses Unix-style device names instead of Windows-style device names. You will need to convert Windows' PHYSICALDRIVEN value to the correct Unix-style device name: \\.\PHYSICALDRIVE0 = /dev/sda \\.\PHYSICALDRIVE1 = /dev/sdb etc. In this example, the device name of the Xbox hard drive is /dev/sdc Now, check the current lock status of the Xbox hard drive by entering the following command at the DOS prompt: smartctl.exe -g security /dev/sdc (Remember to substitute the correct device name for Xbox hard drive attach to your PC. It may be different than given in this example.) To unlock the hard drive, issue the following command: smartctl.exe -s security-eeprom-unlock,eeprom.bin /dev/sdc Note: The eeprom.bin file MUST BE in the current working directory. One last time, check the unlock status of the hard drive: smartctl.exe -g security /dev/sdc Remember to use the correct device name for your PC-attached Xbox hard drive. If the hard drive is power cycled, it will again be locked. With the commands above, the locking password is not removed. The drive is simply unlocked to gain read/write access to its content until an IDE bus reset or power cycle occurs.

Is the locking password all 1's or the configuration EEPROM's HDKey value?

A1: Yes. A2: From the factory, a unique HDKey value is stored in the 256 byte (2048 bit) serial EEPROM - configuration EEPROM 24C02. It is used along with the hard drive's model and serial number to cryptographically compute the password to lock and unlock the hard drive. A stock Xbox has a unique HDKey stored in its configuration EEPROM. The hard drive was locked at the factory with the correct password computed for this Xbox and the particular model and serial number of the hard drive installed in it.

How is your Xbox modded? If softmodded, some softmods use a virtual EEPROM. This virtual EEPROM gets updated in RAM with the new all 1's key and the hard drive locked with its computed password. However, the data in the actual EEPROM chip on the motherboard did not get updated with the new key - only the virtual EEPROM (RAM copy) of the EEPROM's data was. Thus, after rebooting, the Xbox still computes the password using the original non-all 1's key it originally contained but the hard drive is actually locked with the password computed using the new all 1's key. Therefore, error 06.

Connect this adapter to your PC and see if usbview.exe is able to obtain the USB descriptor information from it. The adapter may no longer be working. usbview.exe

XBHDM ???. Which version of XboxHDM are you using to lock the hard drive: XboxHDM23USB Beta 2, 3 , 4 or XboxHDM v1.9? Or, are you using some other application to lock the hard drive? How's the Xbox hard drive connected to your PC?

I don't recall having any problems with it downloading from another Xbox on my local home network or even when connecting to remote FTP servers on the Internet.

UnleashX has an FTP client built into its File Manager. To use it, you have to enable it from the Select menu in either the File Manager's left or right-hand pane. Once selected, you are able to enter the IP address and login information for the remote (other Xbox's) FTP server to download files to the selected destination path selected in the other pane of the File Manager. imgur.com photo album: UnleashX's FTP Browser Mode (FTP client)

The latest release I ever found was 0.5 (fixed). I was never able to find this elusive 0.7 beta release. Wayback Machine archived copy of www.dextrose.com's dx-dexbe-0.5.fixed.zip.

There is no G drive available on a 10GB stock hard drive. For unmodded Xboxes, there's no access to an F or G drive. The original stock 8GB hard drive is split between the stock partitions C, E, X, Y, and Z. No extended partition 6 (F) or 7 (G) drive available. Those partitions are only accessible on larger hard drives. Generally, F up to the old LBA28 137GB hard drive maximum size limit and G the additional space available beyond the 137GB limit for larger than 137GB HDDs. However, there are other items to consider when creating larger partitions without errors occurring at a later time. For example, an extended partition formatted with 32KB clusters supports a maximum partition size of 512GBs. If you create a partition over 512GBs using 32KB clusters once more than 512GBs of data is written to the drive, the partition will be corrupted. Start over formatted all of the extended partitions and writing the data back to them. Cluster size - max properly supported partition size 16KB clusters - 256GBs 32KB clusters - 512GBs 64KB clusters - 1024GBs (1TB)

The original Xbox hard drives were 8GBs. Some Seagate hard drives later in the production cycle changed to 10GBs; however, for the Xbox only 8GBs were used. You can prep/format the additional 2GBs to get a small ~2GB partition 6 (F drive). However, access to F may not be enabled in the replacement dashboard. Each has its own setting to enable access to the F partition. Make sure access to F is turned on. I know that both Evoxdash and UnleashX have such settings. XBMC however, may not, it simply looks for all possible partitions and if properly formatted adds access to it. Download XBMC's xbmc.log file. Post it at pastebin.com and add a link to it here so I can look through it for any errors.

CDX is a multi-game disk loader application. You create a disc with multiple games (as many as can fit on a DVD-R disc) that has a selection menu. You can change the background images for the selection menu and game loading screen. I believe he wants to modify the look/background image that CDX displays while the game you selected to play is being loaded from disk. CDX is the menu application on many original Xbox game disc's that displayed the menu for the additional content on a game disc for trailers and game demos available on the disc. IIRC, it was also used to create the menu system for the Original Xbox Magazine (OXM) demo discs and Microsoft Exhibition discs. Edit: And, what digiex.net's harcroft used to create the Offline DLC installer menus. Maybe. Not too sure about this one.

The old tutorials mention the drive must be Rev T or F. I see one of the eBay listings that says Rev. B. From what I've read from the old tutorials this Rev. B version may not work. I think the Rev. F version you found should; however, is the picture for the listing the exact model of drive you will receive ???. It may not be if they have several and just pick one out a large batch of drives they have available. Verify with the seller that the model pictured is the drive model you will receive. Link to the old xbox-scene.com website's Wayback Machine archived DVD Drive modification web page: Xbox Hardware Addons/Modifications Guides > DVD-drive modifications Link to one of the many Samsung drive modification tutorials listed there: Detailed Samsung SD-616T or SD-616F drive replacement tutorial The SD-616T or F do not fit inside the Xbox without, what I consider, major modifications being made inside the Xbox case: Making Your Modded SD-616F/T Fit Inside The Xbox Case

It's attached. READ ME.txt

You uploaded the entire Quick Upgrade folder to the Xbox, not just the default.xbe file? It takes everything in the extracted Quick Upgrade folder for the app to run properly.

There should be an default.xbe file in the extracted content. The latest version as of today is Build v1.1.9. Find Quick Upgrade.zip in the Installer Variants subfolder. Inside the ZIP archive's top level directory you will find a folder named Quick Upgrade and a Read Me.txt file. The default.xbe file along with all the other files that are part of the Quick Upgrade app are inside of the Quick Upgrade folder. Upload this folder to the root/top-level directory of the E drive. Next, with the replacement dashboard's File Manager/Explorer, browse to the file named default.xbe so it is highlighted. Finally, press (A) on the controller to run the Quick Upgrade application.

Enable the Kernel Font for your specific Xbox’s kernel in the NKPatcher Settings app. Edit: I see @Rocky5 already mentioned the fix.

The tsop_m7 BIOS will not work with all BIOSes that you attempt to do a TSOP recovery/reflash. From your experience, it seems like CerBIOS is one of them.