Search the Community

I have 2 original XBOXes, one is v1.6 and I'll eventually add a modchip, and the other is a v1.2/v1.3. I finally got around to fix the corroded traces problem on the v1.2/v.13 by soldering 4 wires from a 80pin IDE cable, it looks much cleaner than using 4 stranded wires I added a used 1TB sATA HDD + IDE to sATA adapter + 80pin IDE cable and used Hexen 2018 or TruHexen 2021 (not sure which) which installed fine. BUT... I know the laser will eventually die and I want to have an alternative method of setting up an HDD, so I picked up a 2nd 1TB HDD and tried XBOX HD Maker 2.3 USB beta3, with the batch file modified to make it work with any connected HDD, not only USB. The steps I did were: - ran xboxhd.bat, option 2 (Launch xboxhdm), then within QEMU, option 1 (Build a new Xbox HD from scratch) - did NOT format partitions because it outputs "Error: out of memory" when formatting F: and then scrambles the entire output and menu, instead I went with option 3 (Format extended partitions on Xbox drive) + 4 (F and G splits space evenly), then 2 (Rebuild C-partition on existing Xbox-drive). When booting the XBOX with this HDD I get a blinking orange light and nothing on screen after the initial boot logo. If I use Hexen to install a Dashboard it works fine, so I know the HDD is correctly partitioned and formatted. The batch installs some files on the C drive, maybe these files are not the correct ones for a TSOPed XBOX?

Hey everyone, So, I set up a Raspberry Pi 2 to read eeprom from a 1.1 board. After more than a few attempts I realized my problems were due to operator error (ie. me). Nonetheless I got it to work and now I can recover eeprom from some boards I have. Excellent. New life skill. I also have some Seagate and WD drives from original xbox that I attempted to use XboxHDM. Hooked everything up through USB adapter (see photo). Here's the issue. I could identify both drives when I connected them. However I could not unlock them. To troubleshoot, I tried a 500GB WD Sata through the same USB adapter and proceeded to setup that drive. I now have the eeprom transferred and a working softmodded 1.1. Great! After more reading, I tried to access the old Seagate and WD drives again. Now I can't identify the drives through XboxHDM even though I did before. I've tried multiple times. Tried every jumper setting on both drives, but no luck. I even tried other versions of XboxHDM. Quite possibly I just ran out of talent and this is more "operator error". Does anyone have any suggestions?

anyone know a work around for usb keyboard, xboxhdm loads fine,them after selecting 1 no further key presses, accepted it does squat. dont want to have to buy a ps2 keyboard. thanks.