KaosEngineer

The Xbox is very finicky about which USB thumb drives it works with. Not exactly what it doesn't like. I have no problems using old generic 64MB keys but even some older 1GB keys don't work. I've heard that using an SD-to-USB adapter with a <=4GB SD card works well. (I have not tried it as my old 64MB USB Key works well 4 me.) There are specific settings you have to use with drivedroid to get it to work. Read the tutorial at https://www.reddit.com/r/originalXbox/wiki/drivedroid

Read Grimdoomer's blog on using a Raspberry Pi and PiPROM software to read the Xbox's serial configuration EEPROM data: Read/Write an Xbox EEPROM with a Raspberry Pi You use SDA, SCL and GND pins of the Raspberry PI's GPIO connector.

The newest XboxHDM23USB Beta 2 starts in Windows and runs Linux under QEMU. The Linux build does format and writes to the FATX partitions. (Xbox HDD connected to the PC via a USB-to-HDD interface adapter as delivered. For SATA HDDs, the scripts can be modded to use a PC's SATA ports instead. However, the user has to make sure they work with the correct HDD else they format their PC's OS drive.) The older versions, XboxHDM v1.9 or v2.2a boot from CD or USB key and they too, I think, start QEMU to boot Linux to prep the Xbox HDD. Xbox HDD connected to a native IDE interface on the PC's motherboard. You need the Clean_C_and_E_files_for_Xbox.7z archive that was hosted at theisozone to add the files from it to XboxHDM's folders hdm/C and hdm/E (well E's not really important a couple of empty folders that the Xbox will create on bootup if not found.)

Ok. I think that ISO was just patched to allow playing the offline missions without requiring an Xbox Live account on the console. It didn't also have the online missions patches applied to play them offline as well. Here are a few more: [Mod] Phantasy Star Online Episodes 1 & 2 ( Episode 4 Wilds area test) PSO1_PSO4_v0.01.7z The link was already removed as being dead. and [Mod] Grand Theft Auto: San Andreas [NTSC] (Uncut) [EP Hosted] Links Code: http://50.7.136.26/bks/zorlon/Grand Theft Auto San Andreas (Uncut).7z.001 http://50.7.136.26/bks/zorlon/Grand Theft Auto San Andreas (Uncut).7z.002 http://50.7.136.26/bks/zorlon/Grand Theft Auto San Andreas (Uncut).7z.003 http://50.7.136.26/bks/zorlon/Grand Theft Auto San Andreas (Uncut).7z.004 along with the patch file http://50.7.136.26/bks/zorlon/GTASA addon A v1.0.7z

Had you also downloaded Zorlon's pre-patched ISO version. It was a three-part 7-zip archive: This is hacked so you do not require xbox live to play the offline mode Phantasy Star Online.iso - 1.73GB Code: http://50.7.136.26/bks/zorlon/Phantasy Star Online.7z.001 http://50.7.136.26/bks/zorlon/Phantasy Star Online.7z.002 http://50.7.136.26/bks/zorlon/Phantasy Star Online.7z.003 Above links are offline. Source: https://www.epforums.org/showthread.php?61746-Phantasy-Star-Online-Episodes-1-amp-2-NTSC-U-(Cracked)-EP-Hosted&highlight=phantasy+star+online+iso

Thanks @nikeymikey I see that it was recently added, 1 Aug 2019, to archive.org's XBHomebrew download section along with several other new additions.

The file is actually a 7-Zip archive, not a standard zip file. Windows' built-in zip extraction doesn't know how to extract a 7-Zip archive. The file should really be named: Greg Hastings' Tournament Paintball [NTSC-U] [HDD Fix].7z WinRAR and 7-Zip archive tools check the magic number in the file header to know which extraction routine to use, not just the file's extension.

Been looking for these for a long time. All of the download links Zorlon posted are offline. You now need to find a copy of Mad Dog McCree for the Xbox ported by jago138.

Flip the switch on the DuoX2 and boot the other bank. Not exactly sure which BIOS it may have on it. Generally, I always thought a v1.6 Xbox BIOS would boot on a 1.0-1.5 version, not recommended to leave it this way but reflash with a 1.0-1.5 BIOS. Booting to the MS dashboard indicates that your replacement dashboard is stored in a different location than the BIOS is attempting to load. The MS dashboard is the final dashboard attempted if all others in the boot order list fail

How is your Xbox modded? The hard drive will have to be UNLOCKED for the PC and HDD Raw Copy to read the content to create the backup. Select the type of backup file to be created: - .imgc - compressed backup - .img - uncompressed backup

The dashboard is an Xbox executable file - xbe extension. Most modified BIOSes try first to load the file evoxdash.xbe from the root of the C drive. There are other dashboard files tried if that one is not found finally, the xboxdash.xbe file is tried if none of the replacement dashboards are found on the hard drive The path to these boot order dashboards can be modified from their default values a custom version made of the modified Xbox BIOSes

Possibly reparable but not an easy fix. The second picture is a resistor pack that contains 4 - 33.0 ohm (corrected the value) resistors. What was connected to the IDE cable when the problem occurred? Did you have the cable inserted backwards? That should be near impossible to do with proper cable keying. However, some cables have no keying to prevent it.

What version is the kernel? There are many different X2 BIOS / Kernel releases. Each has a different number assigned. I believe 4979, 4981, 4983 are the last three (256KB sized X2 BIOSes). There are many before these. And, the latest 512KB release is 5035. Depending which dashboard and skin setup yo may see if on the dashboard screen. If not, go into the replacement dashboards settings page(s) to find it. Kernel version: 1.0.KKKK.NN

Try booting the recovery FlashBIOS 3.0.1 or 3.0.3 for a 1.6 Xbox (hold both power and eject to power on the console. the front switch panel’s X3 logo should look purple and the FlashBIOS screen should appear on the TV screen) to flash the X3 BIOS to the modchip.

Read grimdommer’s blog about using a RPi as an Xbox EEPROM reader here.

With that Aladdin XS modchip, you may have to hold the power button for 5+ seconds to disable flash protection. If all the right connections are made to the front panel LEDs, it may start flashing or just do it one time to indicate when write protection has been disabled.

Do you have the external switch board?

There’s already a pin header socket on the modchip to plug it onto a pin header soldered into the LPC Debug port of the Xbox. No need to remove the pogo pins. Turn it upside down and connect it to the pin header. Follow the traces on the PCB to make sure you have it connected the right way around. Oh by the way, it looks like an X2.3 lite+ See: http://web.archive.org/web/20070103070551/http://www.xbox-scene.com/modchips/x-ecuter2_lite_plus_pictures.html For specs, read the Xecuter Lite Plus 2.0/2.2/2.3/2.3b column at: http://web.archive.org/web/20070203080852/http://www.xbox-scene.com/modchips3b_table.htm

Use XBPartitioner's Help feature (press the Back button) to find which button / control is used to change the selected partition's size. If all space is allocated to the partitions you can't use it elsewhere. You must decrease the size of partition 7 (I see partition 8 selected / highlighted, not 7 to make a change) to then reallocate it to partition 6. However, the A button should cycle through the standard LBA48 setup schemes for partitioning the hard drive. All to partition 6, partition 6 up to 137GB / partition 7 takes the remainder, partition 6 up to 137GB / No partition 7 or equally split between partition 6 and 7. While running XBPartitioner from the Hexen 2019 disc depending on the BIOS it uses, you may not be able to make any changes. Copy / install XBPartitioner v1.3 to the hard drive's applications folder, remove the Hexen 2019 DVD, reboot into the replacement dashboard running from off the hard drive and start XBPartitioner v1.3 from there. Update: Is your controller an OEM MS controller or a third party one? Does the Back button not work to bring up XBPartitioner's Help page?

ERROR_PATH_NOT_FOUND 3 (0x3) The system cannot find the path specified. I'm not exactly what path it's trying to write to. If it was the configuration file, config.xml, it was read to set up the menus of the UnleashX dashboard. So, it should not have a problem writing to it. However, I don't recall seeing any such information in that file for screen calibration data. The replacement dashboard must be trying to write it elsewhere; but where? The skins folder, the path to where UnleashX's default.xbe or other named XBE file is running from. Both of those should be known. Update: There should be a UDATA folder present that stores information used by UnleashX. E:\UDATA\9e115330 Did you delete that folder? Is it present on the hard drive? Video calibration data may be in the file: E:\UDATA\93115330\0064122817A8\videoset.dat A 144-byte file on my console.

And, the SMD transistor (Q7C2) between the clock cap and Xyclops chip had 3.3Vdc present on the collector (pin labeled C below). ____ B --| | | |-- C E --| | ------ Updated: Added a better picture of the transistor from the ONSemiconductor datasheet. They are one manufacturer of this part - MMBT4403LT1 (part labeling 2T). Another Xbox Repair Manual states that the replacement part is an MMBT3906LT1 (part labeling 2A). Odd, not sure why it would not power on. Next, check the voltage level present at the PowOn control line of the motherboard PSU connector. Does it go high (3.3 or 5Vdc) when you press the power button and is low (0Vdc) when not pressed?

Thanks for measuring the voltage levels. I guess part of the system does still have 3.3Vdc in standby (while off). MS changed the voltage supply level that runs to pin 6 of the LPC debug port. Pre-1.6 consoles have a switched 5Vdc level while 1.6 versions have a constant 5Vdc present as long as AC power is connected. The 3.3Vdc must still run to the clock circuitry as it did in previous versions of the console. I need to see if I can track down (someday really soon now ) where the 3.3Vdc blue wire runs to on the motherboard.

Error 06 - hard drive cannot be unlocked. From XBOX Error Codes Explained- Go Here First! 6 - kernel - Cannot unlock HDDIf you understand the above, you should be able to understand what this means. It means you are trying to boot up the xbox with an harddisk that is locked in combination with ANOTHER motherboard than you are using it with right now.What can i do about it, you ask? Well place the harddisk back in the xbox where it came from. After that, UNLOCK the harddisk with the same procedure i explained above (see error 5). Now when the harddisk is UNLOCKED, put it in the xbox which gave you the error. Now when you boot up with the chip ON it should not give you an error anymore.However when you put the xbox on with the chip OFF your xbox will give you an error. (error 5) So to make sure you can boot original and boot with the chip ON. Next do the same as above: "Boot up your xbox with the chip on. Preferrably with a slayer evo-x cd. Now you choose "Eeprom management." Than you choose: "Lock hdd." It takes one second. After its ready it should say something like "Done"When it is ready just turn off your xbox. Disable your chip and try to boot original. Now there should be no more error. The wrong HDDKey was used to lock the hard drive for the Xbox you are trying to instsall it in.

Does the eject ring start flashing orange and the fan speed increases to 100%? Those are signs of detected overheating by the System Management Controller in the Xbox.

2T is an MMBT4403LT1G Ic max 600mA 2A is an MMBT3906LT1G Ic max 200mA