KaosEngineer

Title updates are were made available via Xbox Live. They were updates to a game to fix bugs etc. These title updates are applications to run to install the update as Xbox Live is no longer available to download them. Download the files and I suggest uploading them to your Applications (Apps) folder and run it to install the games title update. The game being updated has to already have a save present on the hard drive. You have already played it and saved the game before running the Title update application. The same is true for using the DLC installers.

Any of the latest releases will work with it: x2 4981 (v1.0-1.5) x2 4983 (v1.0-1.5) x2 5035 (v1.0-1.5 and 1.6) iND-BiOS 5003 (v1.0-1.5) iND-BiOS Beta Feb-11-05 (aka 5004) (v1.0-1.5) Evox M8 plus (v1.0-1.5 and v1.6) Which to use depends on the version of Xbox you have. Most of these work only on 1.0-1.5 Xboxes; however, a couple have a specific 1.6 release too. There are .06 and .67 LBA48 configurations available too. 06 - F only or 67 for F and G support. No reason not to use the 67 version even if you only format/partition a larger hard drive to use only F. 67 release must be used if the new larger HDD is over 1TB in size.

I have no info on that.

Boot the Xbox with an unmodded CPLD code Aladdin XT plus 2 modchip, then swap the entire modchip with the Aladdin XBlast CPLD reprogrammed chip with the 1MB SST49LF080 flash memory chip installed in place of the 256KB SST49LF020A. It takes two entire modchips to do modchip hotswapping.

THe file does seem to contain a lot of extraneous and unneeded files making it much bigger than necessary.

It is in the first post of this topic thread. And attached below: XVGM.rar.torrent

Okay, I have that same ind-bios.cfg file on my Xbox. I'm using a Western Digital 320GB IDE hard drive. From power on till UnleashX's menu appears is ~10 seconds. Well its really hard to tell with my current configuration - X3 modchip with X3 BIOS running- then booting into ind-bios The loading ind-bios message stays on the screen for about 6 seconds then the iND-BIOS white splash screen appears for less than a second then UnleashX's splash screen followed by its main menu appearing. Oh, wait I have to change the DIP switches to select bank 8 that I have flashed with ind-bios 5004.67. Update: I changed the DIP switches to select bank 8 and power cycled to boot ind-bios 5004.67. The time from power on until UnleashX's main menu appeared is ~20 seconds. ind-bios loading ~6 seconds flubber animation ~6 seconds ind-bios splash screen 2-3 second UnleashX splash screen 1 second then fades a few more seconds (2-3) - the time here depends on how many files are installed on the hard drive - the more apps present the longer it will take. I hear the disc drive seeking a lot as UnleashX scans the hard drive folders set up to create the menus. then UnleashX's main menu appears After changing the bank select to boot ind-bios 5004.56 directly, it seems strange that the length of time the ind-bios splash screen is displayed increases a couple of seconds as compared to loading ind-bios from the X3 Config Live (X3CL) Bios Tools menu. No flubber animation is displayed between loading ind-bios and the white ind-bios splash screen. It was already displayed while booting the X3 BIOS before going into the X3CL menu.

Not sure why the modchip would be flashing too. Red/orange is a RAM error. Make sure there are no bits on conductive material between pins of the RAM chips or any of the traces leading to them. It could be one of the DDR DRAM chips has gone bad too. There are 4 on top and 4 more in the bottom of the motherboard.

Strange I don't think it should take over 30 seconds total from power in til the dashboard is up and running. Do you have an ind-bios.cfg file in the root of the C drive?

https://assemblergames.com/threads/mod-aladdin-xblast.55068/#post-793422 So, you should be able to flash it if this Aladdin XT clone has the same CPLD pin usage as the one's he'd been reprogramming the CPLD chip on. Does the Aladdin XT plus 2 look like this one:

Great! Time to fill it up.

Did you also delete the game save folders under E:\UDATA and E:\TDATA? If present, the specific folder to delete under each is: 54540082

Use a 256KB BIOS iND-BiOS 5004 F and G (aka Beta Feb-11-05) You don't have to use a 512KB BIOS just because your TSOP flash memory device can support one. 1.0 and 1.1 Xbox's have a 1MB TSOP packaged flash memory chip that holds the BIOS/Kernel. For a 256KB BIOS, the flashing software writes 4 copies one after the other to fill the chip and for a 512KB BIOS two copies. Note: Not all flashing software writes multiple copies of the BIOS file to fill the chip (e.g., GenToox Loader). But I believe it's only used to flash the Sharp brand TSOP flash chip.

Look at the 1.0/1.1 pictures for the two sets of pads to bridge. https://www.biline.ca/xbox_solder.htm The bottom set are most likely R7R4, not R7R3. Not sure why the silkscreen is rotated 90 degrees for R7R4. The pads are not rotated 90 degrees when compared to R7R3's.

Easiest method without soldering would be to place a small drop of conductive glue between the two pads at R7D3 and R7R3 (or is it R7R4) to bridge them together. Looks like there's a resistor already present at R7R3 but next to it there's a pair of unconnected pads.

Looks like the write enable bridge has been removed from the top points at R7D3. I suspect the bridge across the pads on the bottom of the motherboard at R7R3 has been removed too.

Source: https://github.com/gotbletu/wikimd/blob/master/xbox-softmod.md

No, that's ST Microelectronics. Evoxdash can be used to reflash the TSOP. Non-Winbond method listed in Hexen 2018's TSOP/modchip flashing menu.

Nice, you can easily use Hexen to flash the TSOP as long as the write enable points are still bridged together. The top one is at R7D3 right off the edge of your picture. The other is on the bottom of the motherboard at R7R3.

That program doesn't show you the information you need to know. Open up the console and look at the TSOP chip at location: U7D1. You do know that it is booting the Evox D.6 BIOS. It really needs to show you the manufacturerID:deviceID byte values instead of trying to help you by telling you the Chip type which is of little to no help at all.

Oh right, v1.1 listed in UnleashX's System Info page. Need to check the brand of the flash chip on the motherboard. Verify which brand it is: Sharp, ST Microelectronics, Hynix, etc.

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.