KaosEngineer

If that IP address is on your network, FTP to it and download the xbmc.log file from the Q drive in the System subfolder. Note: I've updated the path to the log file. It is not in the root of Q where it is found when running plain old XBMC4Xbox. View the contents of this log file to determine the cause of the Fatal Error and fix it. If you need assistance determining the problem and how to fix it, copy/paste the content of the xbmc.log file to pastebin.com and post a link to it. Update: Actually, the second line on the screen shows the cause of the FATAL error. A file is missing, guisettings.xml, in the masterprofile folder located in the special://masterprofile/, P drive, while running XBMC-Emustation either in safe mode as you are in or when fully operational and connected via FTP. If you were able to see that folder in XMBC-Emustation's File Explorer, it is displayed as the Profile directory. Update: How did you install XBMC-Emustation? Files uploaded after properly building it from the xbmc-emustation github repository or from the latest pre-built archive available at xbmc-emustation.com.

When you were softmodded, the eject fix was patched into the kernel. The M8 BIOS does not have the eject fix patch. Many Moons ago, during the height of the xbox hacking scene, I seem to recall someone had released an M8 and/or M8+ BIOS with the eject fix (EF) patch applied to the BIOS. I have not found a copy of that file though. I believe that Team Xecuter's X2 4981 BIOS and possibly a few others can be modified to disable the Reset on Eject (have the Eject Fix patch applied using XBTool v1.0.23a). Or, X2 4981.xx and X2 4983.xx already has the EF patch built in.

Hmm, Rocky5 just mentioned something about the HDDKey value showing incorrectly for a 1.6 console. I need find that post. I believe it was in the his Bugs forum here at ogXbox.com. Update: It was on reddit.com not ogxbox.com where he posted that statement: (Bright light ahead)

Check the DVD power/control (generally an all yellow wire cable connected from the motherboard to the DVD drive) to make sure there are no bent pins inside the connecting header on the motherboard or the DVD drive itself. A broken wire could prevent the tray open/closed status from being properly read. This picture is a poor representation of the actual motherboard connector as it has 14 pins but the next two pins 13 and 14 after 11 and 12 shown have no wire or connection made to the motherboard. Only the first 12 pins are used. The connector on the DVD has only 12 pins.

Which BIOS is installed? Not all support the feature: Eject Fix - the Xbox will never reset if you press eject-button The stock BIOS resets the console when you press the eject button. Feature List Table of all (well almost all) modified Retail Xbox BIOS releases:

Once NULLed, Config Magic 1.6.1's Unique HDD Key value is the the 16-byte key that should be shown as 32 zeros. Near the bottom of the page, the CURRENT HDD UNLOCK PASSWORD with the current lock status of either LOCKED or NOT LOCKED is displayed. This value is the 20-byte long unlocking password sent via an ATA security command to the drive to gain access to the drive. It is not zero. For a softmodded console, the lock status has to show LOCKED. It is a requirement of the stock BIOS that the hard drive be locked. A hard modded console does not require the hard drive to be locked but it can be. For the console to boot to the stock dashboard with the modchip disabled, the hard drive has to be locked. When the modchip is disabled, the stock BIOS is being used to boot the Xbox. Thus, the hard drive must be locked. The same as required by a softmodded console. However, the Xbox can only run the stock dashboard and signed applications as the console has no exploit breaking the security features of the console's firmware.

The HDDKey is NULL (0x00); however, the locking password is NOT. (Here's where the name of these values gets confusing.) The Xbox's HDDKey is 16 bytes - 128-bits long. The computed unlocking password is 20 bytes - 160-bits long. It is not stored anywhere on the Xbox. The value is computed by the BIOS each time the console boots. From the factory, every Xbox had a unique HDDKey stored encrypted in the configuration EEPROM, (see: https://xboxdevwiki.net/EEPROM for information about the contents of the configuration EEPROM). The decrypted HDDKey value is one of three parameters passed to the routine that computes the unlocking password. The hard drive's model number and serial number are the other two parameters passed to compute the unlocking password sent to the hard drive via an ATA security command to gain access to the hard drive's content. Until the correct unlocking password is sent to the hard drive, the hard drive cannot be accessed. There are two passwords for the hard drive. A MASTER password and a USER password. The MASTER password can be used to unlock the drive or the USER password. The Xbox's algorithm computes the USER password. I believe the statements made above are correct. If not, let me know.

Sorry you are correct. If you have an SST flash chip you should use the 3.2.x options not 3.3.x (THe reason I mentioned those 3.3.x options were for the BIOS version they were going to be flashing to the modchip.) From your set of pictures, I thought the 3.3.1-3.3.8 were for the SST chip, not Winbond or Sharp. Update: The 3.2 menu option will definitely work for your mochip. However, I think 3.3 will work as well since your modchip has a 256KB flash memory chip and does not require the BIOS files to be resized (duplicated) to fill the chip.

The BIOS currently on the modchip is X2 4979.06, with the MD5 hash of 56be0f0146d1a69c0f1e6fa9a9558394 as seen in the first picture - the output of Bios Checker v5.0. You can see this Kernel/BIOS number in the UnleashX System Info page as the Kernel Version value = 1.0.4979.6. The modchip you have uses the SST 49LF020 (256KByte) flash memory chip. You can therefore only use a 256KB BIOS. Any of those listed for the v1.0-1.5 using F and G will work. However, all you have written to the F drive will be lost. Not that it really matters as once 1TB of data is written to the F drive any more will written will corrupt files already present making them or other directories disappear. You have many options that will work: iND-BiOS 5003.67 - Option 3.2.1 iND-BiOS 5004.67 - Option 3.2.3 X2 4981.67 - Option 3.2.5 Evox M8+ (F and G) - Option 3.2.7. Update: HeXEn 2019 menu options stated above corrected for the SST 49LF020 (256KB BIOS for v1.0-1.5). The iND-BiOSes have a configuration file stored on the hard drive and take a bit longer to boot as the hard drive has to be ready and readable before the BIOS can finish booting/loading to a replacement dashboard. But, configuration changes are easier, no flashing of the BIOS required to make changes, not that changes will be needed. I'm not sure of HeXEn 2019's Evox M8+ LBA48 and DVD drive check settings. Similar options will be available with HeXEn 2018 instead of 2019. With 2019, I'd suggest trying iND-BiOS 5004.67 and running XBPartitioner v1.3 to repartition the two (2) extended partitions 6 and 7 each to be 927.78GB in size and using 64KB clusters. Reboot and rerun XBPartitioner v1.3 to make sure that both the F and G (extended partitions 6 and 7 are using 64KB clusters). Start uploading all the files to F and G again.

Never heard of a BIOS damaging an Xbox. It may not boot and will be a bit difficult to flash a different BIOS without having another modded Xbox to fix things or external programmer; but, damage - I don't think so. The kernel version number is what you need to find. Which kernel/BIOS version is installed? Xecuter Rox My Box, etc. on the startup under the big X logo doesn't mean you have an X2 modchip installed. It means you have flashed to and are booting an X2 BIOS from whatever modchip is installed. The HeXEn 2018 disc has the latest BIOSes with the correct LBA48 patches installed for use with XBPartition v1.3.

If XBPartitioner v1.3 says that LBA48 is not found in the BIOS, you need to patch the BIOS to have the latest LBA48 patch applied to it and reflash the updated BIOS to the modchip or TSOP. Which BIOS is currently installed that gives the error with XBPartitioner? XBPartitioner v1.3 will format the 2TB drive with a 1.9TB partition 6 (F drive); however, you will have problems after uploading more than 512GBs or 1,024GBs of data to it depending upon which cluster size is in use. With 32KB clusters, the problem will start after 512GB's of data is written and with 64KB clusters after 1,024GB of data is written. Once you write more than the max supported size, some of the data already written WILL BE corrupted.

From what I read on the compatibility list section at github.com for Cxbx-Reloaded, Brute Force is not supported yet. Not even really listed as a compatible game but one that has issues. Other's have had it run further than you. However, it does not even get to a menu to be able to play it. https://github.com/Cxbx-Reloaded/game-compatibility/search?q=brute+force&type=Issues Update: Other games are reported to have the same issue: IDirect3D::CreateDevice Failed Armed & Dangerous [4C41000D]: https://github.com/Cxbx-Reloaded/game-compatibility/issues/764 ExaSkeleton [4B4B0003]: https://github.com/Cxbx-Reloaded/game-compatibility/issues/436 Conclusion Cxbx-Reloaded is not ready to run Xbox games. A few work but not every one.

The Intel graphics chip is not much of a Graphics Processing Unit (GPU), more like a simple frame buffer driver chip, when compared to a higher-end nVidia GeForce GPUs. I suspect a higher-end GPU with dedicated memory is required to run CXBX-Reloaded well. Check the system specifications recommended to run CXBX-Reloaded. Update: Brute Force may not be compatible/supported yet! From https://github.com/Cxbx-Reloaded/Cxbx-Reloaded: Minimum OS: Windows 7+ x64. 32-bit installations are not supported. GPU: Anything that supports Direct3D 9 (HLE) and OpenGL 3.3 (LLE). Check that the Intel HD 3000 supports the two graphics API requirements - Direct3D 9 or higher and OpenGL 3.3 or higher. For Direct3D run DirectX Diagnostics program - Windows Key+R, in the pop-up run window in the Open box key-in dxdiag then click OK. For OpenGL, you'll need to install a 3rd party application - OpenGL Extensions Viewer from realtech-vr.com and run it.

Yes, it's a text file you can edit to make changes to the settings and menu configuration of UnleashX. Update: config.xml is UnleashX's equivalent to evoxdash's evox.ini. They are each dashboard's settings and menu configuration file.

There's nothing to delete. Q is a virtual drive created when you run XBMC or one of it's variants - XBMC4Xbox, XBMC4Gamers or XBMC-Emustation. You will not see a Q drive when you run a different replacement dashboard such as UnleashX, Evoxdash, AvaLaunch, etc. Download and install the Latest Build of XBMC-Emustation from the web site - http://xbmc-emustation.com

UnleashX’s config.xml file must have been overwritten. Check it’s menu section.

Go into Options and install the Downloader.

Reboot and see if they show up. If not, you will have to edit UnleashX’s config.xml file to add E:\Games to the search paths.

Where did you upload them to on the Xbox: E:\Games, F:\Games, G:\Games in a subfolder for each game? Which dashboard are you using?

The dashboard settings and items listed in the programs, games and emulators menu are set in the replacement dashboards' configuration files for UnleashX's it's config.xml, for Evoxdash it's evox.ini, etc. Was the console softmodded prior to installing a modchip and now the menus have changed booting the BIOS on the modchip?

Look at the System Info page of UnleashX. Press the Y button on the controller from the main menu. To exit - press the B or Back button.

I'd try but I don't think that's the fix. What version of the modded BIOS are you using?

Boot and installer disc - HeXEn 2018 and repair the damage done. First, was the replacement dashboard loading from the E drive? How is your Xbox modded?

UnleashX 0.39.0222A Build 572 is the next to next latest build ever released to the Xbox scene. It doesn't have the FTP root directory listing problem that cropped up in the final release 0.39.0528A Build 584. If games are freezing up, the hard drive could be going out. You may try to clear the cache drives on the Xbox's X, Y and Z drives. Delete all the files and folders in all of them. Some configurations of UnleashX have an menu entry to empty (clear) the cache drives. If you don't like UnleashX, there are other replacement dashboards for the console. Evoxdash but it has no built-in File Explorer to manage/view the contents of the hard drive partitions and is older than UnleashX. XBMC4Xbox v3.5.3 or one of Rocky5's latest renditions of it: XBMC4Gamers or his latest masterpiece XBMC-Emustation Install them in the Applications folder and give each a try. I'd not use the softmod extras disc to to alter settings for a hard modded system (just my preference). However, Rocky5 has been updating the Xbox Softmodding Tool's Extras Disc to work with hard modded consoles too.

What video cable are you using? If using the high-res component video cable, try the standard definition cable with an old TV.