Awesome, I still have a 360 and two OG xbox systems. Maybe you can help me or your software could be supporting setting up a OG Xbox aswell:
Title:
Original Xbox v1.6 Rocky5 softmod HDD upgrade to SATA 1TB: Error 09 after FATXplorer setup
Hi everyone,
I am trying to upgrade an original Xbox v1.6 with a Rocky5 softmod to a larger SATA HDD, but I keep getting Error 09 after installing the new drive.
Console details:
- Original Xbox v1.6
- PAL console
- Kernel/BIOS: 1.0.5838.1
- Softmod: Rocky5 Xbox Softmodding Tool v1.2.2
- Dashboard: UnleashX 0.39.0528A Build 584
- HDD key is set to all 1s:
11111111111111111111111111111111
- Original HDD works and is locked.
- Original HDD is a small Western Digital IDE drive, about 8 GB.
- DVD drive is Samsung SDG-605F.
- The DVD tray has a mechanical issue and often reports “Tray: Open”, but the console boots fine with the original HDD.
Backup:
- I backed up C, E, X, Y and Z over FTP using FileZilla.
- EEPROM backup was created through NKPatcher Settings.
- eeprom.bin, eeprom.cfg and xbox info.txt are saved on my PC.
- C contains the dashboard folder.
- E contains Backups, UDATA, TDATA and the normal softmod folders.
New HDD setup:
- New HDD: Seagate/Samsung ST2000LM015-2E8174, 2 TB SATA 2.5"
- SATA-to-IDE adapter for original Xbox
- 80-wire IDE cable
- FATXplorer used to format the drive as Original Xbox HDD
- Layout chosen by FATXplorer:
C: 500 MB
E: 4.77 GB
F: about 924 GB, 64 KB clusters
G: 0 bytes
- I copied my backed up C contents directly to C.
- I copied my backed up E contents directly to E.
- F has a basic folder structure and some games copied over.
- The drive was password-set/locked in FATXplorer using the 1-filled HDD key:
11111111111111111111111111111111
Important FATXplorer / USB issue:
- I used a UnionSine USB 3.2 SATA adapter on Windows.
- FATXplorer was able to set the password.
- After setting password, FATXplorer said:
“Password set successfully. The HDD will remain unlocked until it is power-cycled.”
- After power-cycling/reconnecting through the same USB 3.2 adapter, FATXplorer could no longer properly read the security status.
- It showed the disk only as “UnionSine USB3.2 SCSI Disk Device”, Model N/A, Serial N/A, Status N/A.
- FATXplorer then gave:
“Failed to check the status. Security status unknown. SMART supported/enabled: True”
- So I suspect this USB 3.2 adapter does not properly support ATA Security passthrough.
Xbox error:
- When I install the new HDD in the Xbox, I get the normal Xbox logo and then:
Error 09 / Service Required
- I expected Error 05 if the drive was unlocked, or Error 06 if it was locked with the wrong key.
- Since I get Error 09, I suspect the Xbox cannot properly identify/init the drive through the SATA-to-IDE adapter.
Connections:
- 80-wire IDE cable:
Blue connector -> Xbox motherboard
Grey middle connector -> DVD drive
Black end connector -> SATA-to-IDE adapter / HDD
- SATA-to-IDE adapter tested/connected carefully.
- Power connectors seem seated correctly.
- I tried to make sure the adapter is not shorting against metal.
- I believe the adapter was set to Master, but I may still need to test Cable Select.
Questions:
1. Does Error 09 in this situation point more to SATA-to-IDE adapter / HDD compatibility than to a dashboard or partition issue?
2. Is the ST2000LM015 known to have issues with original Xbox SATA-to-IDE adapters?
3. Should I try a smaller 1 TB or 500 GB SATA HDD first?
4. Should I lock/unlock the HDD only via direct SATA or USB 2.0 instead of USB 3.2?
5. Could the FATXplorer layout with a 2 TB drive but only one large F partition of about 924 GB cause this, or would that usually cause a different error?
6. Should the SATA-to-IDE adapter be set to Master or Cable Select for this setup?
7. Is cloning the original HDD with Chimp or another older PC/internal SATA setup more reliable than building the drive with FATXplorer in this case?
Any advice would be appreciated. I am trying to figure out whether this is:
- wrong locking/security state,
- bad/incompatible SATA-to-IDE adapter,
- 2 TB HDD compatibility issue,
- IDE cable/jumper issue,
- or a partition/dashboard problem.
