KaosEngineer

If the write enable points on the motherboard are still bridged, you can use Hexen 2018 to reflash it. What version Xbox do you have? You can't use X2 5035 unless it's a 1.0 or 1.1. I suggest using iND-BiOS 5004 67 (F and G). You need to check which Flash memory chip your motherboard's BIOS chip is. There are special requirements of software and software and hardware for Winbond and Sharp brands of flash TSOP packaged devices.

It sure does not look like it's hard modded? Have you opened it up and seen the modchip connected to the LPC debug port? Softmodded or hard modded will boot burned discs if no replacement dashboard has been installed. It will go into the stock MS dashboard. However, if you deleted all the files from the hard drive that would destroy a softmod and it would not longer work. So it must be hardmodded. Kernel version 4817 is not a number I recall for any modified BIOS version. Only one of the stock MS BIOS's. I've not used any of the old Evox BIOSs in a long time to know what Evox's D.6 or earlier BIOS releases show for there Kernel version. Flash a new BIOS to the modchip. Evolution-X kept the MS BIOS version number their BIOSes were based on. Making it harder to ID which BIOS you are using. Other dev teams' changed the number making it easier to ID which version you are booting. Update: Looks like Evox D.6's kernel version is 4817. It has no LBA48 support. (https://ask.metafilter.com/163129/Original-Xbox-modified-with-old-version-of-EvolutionX-EvoX-What-to-do-with-it) Max hard drive space accessible is 137GBs - F ~ 120GBs formatted.

Your booting BIOS doesn't have LBA48 support or an older version of the patch. At the top of XBPartitioner's main screen after the error message, it should show the patch level it found in the BIOS your modded Xbox is booting. Is your console soft or hard modded? If hard modded, reflash your modchip or TSOP (with the one of latest BIOS found on the Hexen 2018 disc). Update: From the information you provided, it looks like your console is soft not hard modded - Kernel: 1.0.4817.1. Which softmod did you install?

Try using the XBlast OS v0.56 XBE version instead of Evoxdash to reflash the Aladdin XBlast CPLD modded modchip. The XBE version is an Xbox application form of the BIOS - dot bin file. Remember, the BIOS file to flash is the dot bin file from the XBlast OS v0.56 archive. From the instructions I've read about modding the Aladdin XT plus 2 modchips, it mentions flashing the SST49LF080 with an external programmer before inserting it into the Aladdin's PLCC32 socket. The XBlastOS itself controls read/write access to the flash memory chip but it's not installed yet to control the CPLD.

XBMC4Xbox XBMC before Team XBMC dropped Xbox support and changed the app's name to Kodi for PC and other supported systems.

I didn't think the x3 erase app deleted the BIOS's flashed to the modchip. It only clears or sets the default values stored in the X3's onboard configuration eeprom chip. I've read about the latest X3 BIOSes having a reset feature (not sure which version after which it was included): Hold A+B+X+Y on cold boot Another post about using the X3 Eraser app and reflashing the modchip using the recovery FlashBIOS at team-xecuter.com - How to fix you EEPROM if mess up with X3 Config Live! A bit dated as it mentions the X3 1959 version of the X3 BIOS, not the latest 3294 version.

What are the names of a few of the files that would not transfer?

Do you have the X3's switch panel attached?

What are these boards? Haven't seen a picture of them. I'm guessing they are for internally installing the Wii2HDMI. Or, are you just waiting for the Wii2HDMI modules themselves?

When installed internally, You can't easily keep the AV port intact with the Wii2HDMI attached. It requires jumpering the MODE pins to select high-definition video output. Now, if you modify the wiring some to have switches instead of directly soldering the required mode lines to ground. The AV port could still be used with a composite or other Xbox video cable. The cable connects the mode pins to the required signal to select the proper video MODE of operation

Evox M8plus's default boot order list (1. check for first, 2. if not found try the next, 3. repeat step 2.: C:\evoXdash.xbe C:\AvaDash.xbe C:\neXgen.xbe (Filenames are not case sensitive for the Xbox kernel.) if these three files are not present on the hard drive, the bios will load: C:\xboxdash.xbe

It's the iND-BiOS Feb-11-05 Beta (aka 5004) dot 06 that bricks consoles, not the dot 67 version. If you have a modchip that supports multi-banks (BIOSes) it's no problem. The Aladdin XT plus 2's (or XT 4032's) however only have 1 256KB bank to hole a BIOS. Since the flash memory chip is socketed, it can be removed and reflashed with an external programmer to repair it. If you flashed 5004.06 to the TSOP, desolder the TSOP flash chip from the motherboard, reflash it and soldering it back onto the motherboard can repair a bad TSOP flash too.

Fan speeding up to maximum speed. The SMC thinks the CPU is overheating and shuts off the console. Although I thought, the front panel LED should be flashing orange too. The LPC rebuild wires with there extra uninsulated ends could be touching the trace that carries the signal to the temp sensor. I've not traced out where the CPU's temperature diode runs on the PCB to the ADM1032 (U6F1).

I don't even think you'd have to connect a wire to the BT pad on the modchip for always-on mode. Depends what type of logic gate input it is tied to. does it get pulled high on its own or just float (it could be either a high or low logic level without connecting it to anything.) 3.3V would mean it's always enabled (could never go low which would disable the modchip). The DuoX2 modchip uses eject to disable the modchip. So, connection to the BT point shown in the installation diagrams is to the Eject button signal. When Eject is pressed to power on the console, ground will be applied to the modchip's BT pad to disable it. Without BT tied to anything, the DuoX2 can never (most likely not ever) be disabled. Again, it depends where the pad is connected to. What type of logic gate input does it connect to. Does it have a built-in pull-up resistor or not. Connection to 3.3Vdc would guarantee it cannot go low.

Enter X3 Config Live (Hold White Button while booting the banks that hold the X3 BIOS) either banks 1-4 or 5-8 (1MB in size). Select BIOS Tools: Press A Select Bios Bank Naming then Press A The list of names assigned to each bank is displayed. Or, Select Bios Bank Select then press A. Select Switch to 256k BIOS then Press A the list of BIOSes stored in all the banks is displayed. Select one and press A to boot that BIOS bank. Note, the X3 BIOS shows 1/4, 2/4, 3/4 and 4/4 next to each 256KB bank. It is a 4*256KB BIOS (1MB). To boot it, you need to go back and select the proper bank size to switch to 1mb, not 256k. The BIOSes in banks 5-8 shown are all 256KB in size. They have no 1/4...4/4 or 1/2...2/2 next to the name that a 1MB or 512KB BIOS name would have displayed next to it. Press B repeatedly to go back to the Main Menu.

If you can boot into the X3 Config Live screen (hold the white button down when booting the X3 BIOS bank either 1-4 or 5-8 and named the BIOSes stored in the banks when they were flashed. The BIOS Tools section to select a BIOSes in the various bank sizes 256KB, 512KB, 1MB, 2MB bank(s) the assigned names of each bank stored when they were flashed will be listed.

Some games sign their saves with a cryptographic signature generated with the HDkey from the Xbox they were created on and cannot be transferred to another Xbox without resigning them with a new signature for the Xbox they will be used on. You have to know the HDKey of the Xbox they were created on and the new HDKey you are going to store them on to re-sign them. Not all games require being re-signed. Here's a list of some that do: Forza Motorsports also has to be resigned. Forza Xbox scene dev's created the Windows App ForzaSign for it.

Not exactly sure what state this Xbox Softmod Installer leaves the Xbox in if it doesn't completely finish the installation. Installation which involves a two or three reboot cycle process?

Does the front panel Eject ring change color before it restarts? Does the internal fan speed up to 100%? Try shortening the wires on the bottom of the motherboard that have excessive length in them used in the LPC rebuild. Each wire should run straight from the LPC header pin to the destination. Try to keep each wire away from all the others as best you can. Don't have them cross over each other. The ends should not have bare metal exposed that could possibly touch other traces on the printed circuit board. Almost every end has too much insulation removed.

Here's an old forum thread - Pcsxbox Compatibility List @ https://www.xbox-hq.com/html/postt23606.html

Yes, on a v1.0 motherboard, R3G1-R3G4 are all 10 KOhms.

Which version of XboxHDM23USB? Beta 3's files/folders with the file named xboxbox.xbe is not the MS dashboard. The files in B3 are a no-original-game-disc-required Xbox Softmodding Tool installer. The version 5960 MS dashboard file set is available in Clean_C_and_E_Files_for_Xbox.7z. Update: Oh, I see you found them to install in the Extras Disc too.

Clone the SATA HDD with CHIMP 261812 like you would the original IDE HDD to a SATA drive/adapter combo. The devices all connect via the IDE interface. Your source drive is the SATA HDD/adapter (MASTER) being cloned to the destination the new old stock IDE HDD (SLAVE) connected to the DVD's IDE connector. The hard drive (MASTER) has to have a partition table written to it for the extended partitions to be cloned correctly. If you don't know if there's a partition table on the hard drive, run XBP Table Writer from the Chimp 261812 github repository.

All electrolytic capacitors have the possibility of leaking and going bad. Thus far, the supercap used on the v1.6 consoles for its clock cap have yet to leak in the numbers that have on v1.0-1.5 consoles. The location of the v1.6's capacitor is different than on v1.0-1.5. Leaked electrolyte from a v1.6's clock cap will most likely cause a different set of problems to occur than with v1.0-1.5 clock cap leakage if and when they do fail.

If you used a component cable and enabled the high-definition modes, the only way to turn them back off is to go into the MS dashboard while the component cable is connected. Those options are not available when using a composite cable (Yellow - composite video, Red/White stereo audio RCA jacks). A replacement dashboard will show the high-definition modes as NO with a composite cable attached. UnleashX's settings are only for UnleashX, they don't change the settings stored in the motherboard's configuration EEPROM. To turn them off, a component high-definition cable/AV pack has to be connected. Without the high-definition cable/AV pack attached, the high-definition settings 480p/720p/1080i are not displayed in the MS dashboard's Video Settings.