KaosEngineer

I suggest downloading it from the google drive repository - many updates since the torrent version are included in it. However, it is missing the Xbox letter "N" named game previews. I think that's one of the largest sets of previews being updated and not yet finished.

What format are your images stored in? PNG, JPG, etc.

I thought those flipped reflections were created by XBMC4Gamers (XBMC) itself using the main boxart images. It flips the Y-axis and processes it using an option in the skinning engine and places it below the box art. However, I'm not exactly sure where to find it in the skin's files.

Oh, there's also XBMC4Xbox with the XBMC Origins skin by Dom DXecutioner @ xbmc4xbox.org.uk. https://www.xbmc4xbox.org.uk/forum/viewtopic.php?f=15&t=4393

There are many different releases from the CoinOPS Project: CoinOPS 6, 7, 8 - Massive, GEMS, Lite, Standalone, etc - so many different releases with these. Dragon HyperVISION 5, 6 Premium NINJA - Gold, Massive, Lite and several NINJA add-on packs. Premium 8 VISION 5 I believe Premium NINJA is the latest of their releases. The YouTube video you linked to uses UnleashX with the XvGM (Xbox video Game Museum) skin along with the Playstation emulator PCSXBOX 22b5 to run Vigilante 8. There are many other emulators as you can see from the menu listing they scrolled through to get down to the Playstation emulator. It's available for download using a torrent from OGXbox.com (a 38.1GB download) or the latest release with many updates applied to the v1.1.1 release from CB-Games' google drive. (He's still working on updates to the Xbox letter N game videos; therefore, it's currently not available from the google drive repository.)

That makes no sense to me. If Cromwell boots and has video output, so should Evox's M8+ BIOS. As @SS_Dave mentions above, are you flashing the correct version of the M8+ BIOS to the modchip. There are two different dot bin files. One for 1.0-1.5, m8plus.bin, and another for 1.6, m8plus16.bin, revisions of the Xbox. Once more, which video cable are you using and TV model and region (PAL or NTSC)? Is it the stock composite video cable that has a Yellow RCA jack for standard definition video out along with Red and White RCA jacks for analog stereo audio out?

I think for the MuppetX, it needs a 1MB (49LF080A) EEPROM instead of a 256KB (49LF020A) EEPROM. Its banks are 512KB (2x256KB) for a BIOS flashed it). I'm not sure if it will load a BIOS file properly with the smaller EEPROM installed in it. The Aladdin XT chips use the 256KB (2Mbit - 49LF020A's). Cromwell is a 256KB BIOS as are the modified/hacked EvolutionX M8 and M8+; Team Xecuter X2 4981 and 4983; and iND-BiOS 5003 and 5004 BIOSes. I don't see why any of these others flashed to the modchip would act any differently - no video output.

Shorten the LPC rebuild wires. Make them just long enough to reach in a straight line without any loops in them. (I've also read they should not crossover each other.) On the top side, looks like pin 11 of the header is busted off or at over half of it looks to be gone, is it? I took another look. Optical illusion on the last picture makes it look broken off but I see it is not. The pin header solder joints need to be reflowed/reheated as most of the solder is sitting on top of the pin. It has not flowed down around the pin and inside the feedthru hole on the motherboard to make a good electrical connection.

The hard drive has to be locked with a properly computed password. Each time the Xbox boots the stock BIOS it computes the password using the HDDKey value stored in the 8-pin 2048-bit (256-byte) serial configuration EEPROM on the motherboard and information read from the hard drive itself. There are applications that use an eeprom.bin file created by reading the data from the configuration EEPROM. Raspberry PI and PiPROM software or Xbox EEPROM reader connected to a PC's 9-pin serial port, not a USB adapter serial adapter as most don't work with the EEPROM reader/writer software - PonyProg. XboxHDM23USB Beta 2 or Beta 3 runs under Windows and can lock the hard drive. As distributed, the hard drive has to be connected to the PC using a USB-to-HDD interface adapter. The scripts can be modified to allow access to the hard drive connected to a PC's SATA port.

EvolutionX's M8 and M8+ BIOSes are some of those special case modified BIOS'es that don't follow the other BIOS dev team convention of adding .06 (.6 displayed for the kernel version's last digit in UnleashX) or .67 to show the LBA48 configuration (.06 - partition 6 only - F drive or .67 - partition 6 and 7 - F and G drives). The Kernel version shown in UnleashX will be 1.0.5838.1. They also kept the BIOS version the same as the stock MS BIOS it was based upon - 1.00.5838.01 (UnleashX leaves off any leading 0 in the value it prints for the Kernel Version). Making one ask, "How the H*LL do I know if it's the stock BIOS or modified BIOS?" You'd need to obtain the MD5 hash value for the booting BIOS. Check is against the known original 5838 BIOS's value. If different, it's Evox (as well Evox M8 has the purple shield in the upper left-hand corner of the screen - unless it has been disabled in EVTool and reflashed the updated M8(+) BIOS to the modchip. Run Xbox BIOS Checker v5.0 to see if it can identify the BIOS version or Evoxdash which will change the Current= line in the file named evox.ini which is the booting BIOS's MD5 hash value. You have to compare the MD5 hash to a list of know BIOS versions to hopefully find a match. Xbox BIOS Checker v5.0's bios id list is incomplete and does not identify all BIOSes. Even then, if the BIOS has been modified using EVTool for custom animation or big X logo colors, custom replacement dashboard paths, or other flags edited the unmodified distribution's MD5 hash will not match that of the running/booting kernel/BIOS.

SPPV over at xbox-hq.com has made available a trial version of R-Drive and 2 disk image files used with it to create a stock Xbox hard drive by writing the image to a new drive. In the Bare Mod subfolder downloadable at the link posted below, he has an 8 GB and 10 GB (no reason to use this file) Xbox hard drive image available. A new hard drive larger than 8 GBs will still need to have the extended partitions created and formatted with the Xbox application - XBPartitioner v1.3. R-Drive Images and Application (R-Drive v6.2 included is a 30 day free trial version.) If the hard drive has to be locked to work, a softmodded console, you still need to have a copy of the configuration EEPROM data so you can use an application to lock the hard drive with the proper password computed for this new hard drive and Xbox combination. P.S. I have not tried using the application or Bare Mod images SPPV has made available.

Be careful installing a 1.6 motherboard in a 1.0-1.5 case. There's an extra motherboard standoff with ground shielding tabs present that is not there on a 1.6 console. You can damage a 1.6 motherboard by simply swapping it into an older style case. The extra motherboard mounting post on 1.0-1.5 cases is between the AV connector and GPU.

In UnleashX 0.37.1218A Build 543, pressing Y from the main menu displays the System Info page for me. It is also accessible by going into the menu System -> Settings then use the D-pad or left joystick to highlight System then press A followed by scrolling down to Xbox Info and press A to show the Xbox Info (System Info) page. The Kernel Version line shows a value in the format 1.0.NNNN.LL. NNNN = BIOS/Kernel version and LL = 1, 6 or 67. 6 and 67 are the LBA48 configuration of modified BIOSes that stored the LBA48 configuration as part of the Kernel version value, not all BIOS's do though displaying only a 1. Stock Microsoft BIOSes display a 1 as well.

Maybe that old version of UnleashX, 0.37.1218A Build 543, has no easily accessible System Info page. From any menu listing on 0.39.0222A Build 572 or 0.39.0528A Build 584, pressing the Y button shows the following page: There's a lot more information than seen on the first page (although the kernel version is displayed on it) by using the D-pad or Left joystick to scroll through the listing. P.S. I'll download the old version and give it a try to see where the Kernel (BIOS) version can be found.

All your problems are not the norm for a modded Xbox. MS dashboard improperly installed if you get error 21 when trying to run it from the replacement dashboard. The 250GB IDE hard drive may be going bad. 9 - kernel - HDD parameters: (PIO/DMA/or size {debug}, certain size minimum is required for debug) Not very common error, please try another harddisk. Most likely when the BIOS queried the hard drive for its size, no response was returned. Eject Ring Color Eject ring red doesn't really mean much as the BIOS and replacement dashboards can be configured to change the color displayed. Flashing Orange and the fan speeds up to 100% is an overheating condition. Flashing Red is a configuration EEPROM error. Flashing Red and Green - after the display of Green followed by console reset then again display of Green and console reset, is a system failure. Not all major components of the console are functioning properly, thus the error screen. The number displayed in the upper left-hand corner is used to assist in determining which subsystem failed. See: XBOX Error Codes Explained - Go Here First!

Check the kernel version shown in UnleashX's System Info Page - Press the Y button to see it. If running UnleashX, it should appear. Press the B or Back button to go back to the main menu. What kernel version is displayed? The BIOS running is not XRomwell - it does not support running standard Xbox applications (XBEs). It was for booting Linux and/or reflashing a new BIOS to the modchip. It is an MS code-free BIOS distributed with modchips for legal reasons. There are many different variations of the Cromwell / Linux BIOS.

Check out https://github.com/Rocky5/XBMC4Gamers/tree/master/Mod Files/system/scripts/XBMC4Gamers Extras/480p Game Loaders It has a patch for Arctic Thunder running in HD on a 1.6 console. Many other games have problems running in HD on a 1.6 that can be patched with this script. There are some games however that can not be fixed by this script to display correctly. See Rocky5's YouTube video: 480p Game Loaders for v1.6 Xbox! The script is here but the readme of this version doesn't mention Arctic Thunder like the readme.txt for the version at github.

Those two links are working now: Xbox ATX Adapter for Revision 1.0 and 1.1 Xbox ATX Adapter for Revision 1.2 up to 1.5 Not sure what was happening a few days ago. Several PCBs I had saved links to were not accessible. There are still others that are not showing up - Xerc2 Xbox ir mod, Xbox LED Underglow PCBs and Xbox LPC Rebuild quick solder PCBs.

I found these two pictures using google search of the front and back PCBs with silkscreen text visible. The back silkscreen is the BOM.

The links were posted by @N64 freak here; however, neither work anymore. @N64 freak must have removed them from that web site.

I don't think the MuppetX will work with a 256KB flash chip. Maybe the previous owner swapped flash chips with an Aladdin XT plus 2 when attempting to mod it to an Aladdin-XBlast modchip. I'm at a loss that a new Aladdin XT+ doesn't boot either. In most cases that I've helped someone fix a FRAGing modchip installed Xbox, the problem arose from a bad connection between the LPC bus and the modchip - a cold or improper/poor solder joint of one or more header pins connected to the LPC Debug port. Possible fix: Reflow (reheat/solder) all the connections and try booting the Xbox again. Post a picture of the pin header soldering on the back side of the motherboard. Seeing it will help to determine if the solder joints are the possible problem area.

The skin.xml file has an option to have preview video sound enabled or disabled. <Preview EnableAudio="False" Left="284" Top="139" Width="300" Height="214"/> Change EnableAudio="False" to "True".

MuppetX Pictures on the Wayback Machine captured from xbox-scene.com http://web.archive.org/web/20060522115014/http://www.xbox-scene.com/modchips/muppetx_pictures.html MuppetX Installation Diagrams: v1.0-1.1 v1.2-1.5 v1.6

The Previews file linked in the YouTube description for the video you posted has the UnleashX skin files included with it. Download the 2.5GB file and you'll have the skin. The Default with Preview Videos HD v1.0 UnleashX skin consists of 2 files: preview.jpg Skin.xml Over a hundred XMV and WMV preview videos are included in that file too.

If the modchip installed has a 49LF020A (2Megabit - 256KByte), it's only a 256KB flash memory chip - 1 256KB BIOS bank. It cannot be a MuppetX with 2 512KB banks. That chip is not large enough. It would need to be a 49LF080A (8Megabit flash - 1MByte) to have 2-512KB banks which actually hold a duplicate 256KB BIOS or 1 512KB BIOS (e.g. X2 5035 v16).