KaosEngineer

What version of Chimp? I think I've asked already if you've posted this query elsewhere. Chimp 261812 from here is the latest. (There have been 3 261812 releases, no version number change.) Does your version state Chimp Loader v1.01 upon startup and prompts you to connect the HDD then press A to continue. If not, get the latest version linked above.

Decipher Xbox Silkscreen Labeling First letter - Component type: R = resistor C = capacitor U = integrated circuit RP = resistor pack Q = transistor etc. The next two a digit then a letter are the quadrant determined by the sections marked on the edge of the board. thus the board is divided into a grid and components inside that square are labeled one after the other. The last digit is the device number for each component of a specific type found inside a particular grid section numbered consecutively (e.g., R6C1 to R6C6 are the labels for the five resistors found in grid section 6C). R6C1 and R6C2 look important. From the thick trace on one side, I'd say a power supply voltage applied to that side of the resistor. R6C1 & R6C2: label 101 = 10 x 10^1 = 10 * 10 = 100 Ohms SMD resistor code calculator C6C1 C6C2 and C6C3 look like decoupling caps. From google.com: A decoupling capacitor's job is to suppress high-frequency noise in power supply signals. They take tiny voltage ripples, which could otherwise be harmful to delicate ICs, out of the voltage supply. They are most likely 0.1 microFarad. Pin 20 of the PIC processor, VDD, is connected to 3.3Vdc standby power that is always on when the Xbox console is plugged into AC power. C6B11: Also is most likely 0.1uF cap but in a smaller SMD package. 50 What part is that in the picture? Are you talking about the 50 you see printed next to the RAM chip. That label is for the pin number at that corner of the chip, not a part. I don't think there is a part labeled 50. The RAM chips, Samsung K4D263238M-QC50, have 100 pins, You can see other numbers around the chip. Pin 1 is indicated by the white dot next to the part number (e.g., U6D1) with other pin numbers going counterclockwise around the chip. Around U6D1 I see 20, 40, 50, 60, 80 and 100 indicated near the particular pin of the chip. 089 - What does it look like? Post a picture of it, please. Does it have many pins or only the two ends like the other resistors on the printed circuit board? If a resistor, it would be 08 * 10^9 = 8GigaOhms.

Modchip allows you to install a new HDD without first cloning it as required by a softmod. It boots a modified BIOS that defeats many of the security protections of the console - region locking, IDE security HDD locked to the specific console's HDDKey with a computed password. Modchip - the HDD does not have to be locked. A softmodded system requires the HDD to be locked since it boots the stock BIOS on the motherboard. Yes

Xenium-OS_V20_User_Manual.pdf Wayback Machine Capture of 4th generation modchips table: http://web.archive.org/web/20050525091340/http://www.xbox-scene.com/modchips4_table.htm Find links for pictures, installation tutorials and other versions of the Xenium OS manual there.

Try it. The info I read said to flash a BIOS to the MuppetX 1. Set the bank select switch to bank 1 2. Flash a 1MB bios dot bin file to the device. I'm not sure if it will/can flash only 1/2 of the 1MB flash chip.

Unfinished South Park game. From what I recall, it is so incomplete there's no game to really play. The menu appears and allows you to select some sections and locks up on others. Textures are not complete, physics engine not complete, etc.

If you want to flash a BIOS, install Evoxdash as an app on your HDD (e.g., in F:\Apps\Evoxdash\). Create a BIOS subfolder and place the BIOS dot bin files in it. Run Evox and select the Flash BIOS option. It will scan the BIOS subfolder and list the names of all the BIOSes it finds there.

Yes, you can add a jumper across the cut. Remove the modchip and the onboard BIOS should boot.

D0 does not have to be connected on a 1.6 console. D0 is an output from the Aladdin chip. It should not be tied to ground. It grounds the D0 point for 1.0-1.4/5 Xboxes. Not required to be connected to D0 on the motherboard for a 1.6 since it always boots from an LPC connected device be it the Xyclops chip or the modchip. Cutting LFRAME prevents the Xyclops BIOS from loading.

No, the X2 BIOS is not hard to color change. XBTool can be used to make the color modifications to the flubber. There's also a color preset maker - see http://the-eye.eu/public/xbins/XBOX/PC Based Applications/bios tools/XBtool Color BIOS Preset Maker/

If the other consoles are softmodded you'll need to lock the HDD by having a copy of the eeprom.bin file from each console and using XboxHDM23USB Beta 2 to lock it. To use XboxHDM23USB, you need a USB-to-HDD interface adapter to connect the drive to your PC. If the consoles are hardmodded, you do not have to lock the HDD. Or, purchase a dual drive dock but make sure the device supports sector-by-sector cloning and not the new faster filesystem cloning. Filesystem cloning will not work since the dock will not recognize the FATX filesystem on the Xbox HDD.

I'm not sure if it will work on the Muppet-X. From what I recall when I selected a bank on my X2Pro and flashed with Evoxdash, only that bank would be flashed. The X2Pro has 1MB of flash with bank selection of either 4 - 256KB banks, 2 - 512KB banks or the entire 1MB. Evoxdash would resize the BIOS to fit the space of the bank selected - meaning duplicate it enough to fit the entire selected bank size.

There's a small writeup about the MuppetX modchip at xbox-hq.com: https://www.xbox-hq.com/html/article1692.html Wayback Machine captures of various installation picture pages from xbox-scene.com: v1.0-1.1 v1.2-1.5 v1.6/1.6b It has a 1MB flash chip on it - SST49LF080A but I don't see where you select the bank to boot from if it actually supports more than 1 bank. Update: I see now the switch on it is the bank select switch, not to enable/disable the modchip, but to select one of the two 512KB banks. From what I've read, flashing the chip with Evoxdash use a 1MB dot bin file with the BIOSes combined into one file with the bank select switch set to bank 1. copy /b 512KBBIOS1.bin+512KBBIOS2.bin my1MBbios.bin If the BIOS 1 and 2 are actually only 256KB then create the two 512KB BIOS1 and BIOS2 files: copy /b 256KBBIOS1.bin+256KBBIOS1.bin 512KBBIOS1.bin copy /b 256KBBIOS2.bin+256KBBIOS2.bin 512KBBIOS2.bin Or much easier using the Xecuter2 BIOS Manager (X2BM) and load the first 2 banks with the same 256KBBIOS1.bin file and the last 2 with the second 256KBBIOS2.bin file. Select all 4 banks and save the new 1MB dot bin file.

Evox +3935 is the latest release of that dashboard. There are other dashboards available. The most prevalent being UnleashX 0.39.0528A Build 584. It has an FTP server bug that lists random date strings in the root directory listing making it impossible to double-click on them to browse with the FileZilla FTP client for Windows. And the previous version 0.39.0222A Build 572 that doesn't exhibit that problem. Other dashboards include XBMC4Xbox v3.5.3 and Avalaunch 0.49.3.

What version of XBMC is it running? It may not be present in older versions. I'm running XBMC4Xbox v3.5.3. Oops, it states the kernel as the Operating System version Hexen runs the UnleashX dashboard and its System Info page will show you the kernel version. Press Y to display the page after the main menu appears. Use B to exit back to the menu.

First, you need to determine if you are softmodded or TSOP modded with a hacked BIOS. XBMC system info page shows the kernel version, what value is it? Does the starting flubber animation show Microsoft or other text under the BIG X logo at the end? Evox BIOS generally shows a purple shield with the text Evo X in it.

You can use that HDD if you install a modchip; however, from what I understand about their firmware if bad sectors start appearing they are just ignored instead of being remapped. Thus, not recommended to use a QuickView HDD but it can be. The modified BIOS booting from a modchip does not require the HDD to be locked. Aladdin XT plus 2 on eBay for 3 to 5 USD.

Front panel LED error codes: The FRAG (Flashing Red And Green) condition, next to the last line, the fault condition of Digital Core error is a bit cryptic but means any major system component failure CPU/GPU/BIOS/other caused the system to fail to boot. Therefore, this error is displayed on the front panel eject ring.

Leaked electrolyte can damage the 4 very thin traces on the bottom side of the motherboard that carry the power and eject button closures and red and green front panel LED control signals to the System Management Controller (an always powered on PIC processor). See: http://diy.sickmods.net/Tutorials/Xbox1/Power-Eject_Pinouts/ for information on testing and repair.

For the 1.0 with the weird startup problem and no video. It could be a problem with part of the BIOS in the TSOP flash chip. The 1.0 and 1.1 have a 1MB flash memory chip that holds 4 copies one after the other. The actual BIOS is only 256KB bytes. Adding a wire or two to force an Address line low to load from one of the other banks can sometimes make such a comatose console boot properly. One of the old Xbox resellers posted information on their site now long gone but the Wayback Machine (archive.org) has a capture of that web page. The Wayback Machine capture of llamma.com's coma console fix tutorial.

Welcome to the world of ogXbox modding. Mod it or lose it, KaosEngineer

Is the HDD by any chance a Maxtor Quickview 250GB IDE HDD? If not, what model is it? They cannot be locked which is required for a softmodded Xbox. Some IDE drives don't lock.

What media is it burned to DVD+R or DVD-R? Not all drives like DVD+R media. Try DVD-R if not already burned to that media type.

Yes there's a problem in official release of UnleashX 0.39.0528A Build 584. The previous version 0.39.0222A Build 572 does not exhibit this problem. I also think that if you use Build 584 as an application run from XBMC after letting that dashboard set the time/date UnleashX Build 584 doesn't have that problem either. It's just when UnleashX uses NTP to set the time from the Internet that the problem occurs.

I'd not tested it but the files from the source have been good before this one. Thanks for the info. I removed the BAD content from my previous post